A valid SCM URL format appropriate to the SCM provider without the "SCM:Provider:" prefix. The new location to record a tagged release. The "SCM:Provider:" prefix is used to determine the provider being used. A valid SCM URL format appropriate to the SCM provider. The current location of the development trunk. In the previous example maven was supplied with the current location of the development trunk and the new location to record tagged instances of the project. When using the release:prepare goal, the user must supply maven with information regarding the current location of the project's SCM. DtagBase=file:///D:/subversion_data/repos/my_repo/my-app-example/tags The commandline example directs the plugin to locate a Subversion SCM on a local file system. The following example shows how to run the release:prepare goal with a Subversion SCM. Tag the entire project source tree with the new tag name.Modify and commit release information into the pom.xml file. Prompt the user for the desired tag, release and development version names.Verify that there are no uncommitted changes in the workspace.The plugin will record release information into a new revision of the project's pom.xml file as well as applying SCM versioning to the project's resources. To create a release the maven-release plugin is executed through maven in 2 stages: The plugin provides basic functionality to create a release and to update the project's SCM accordingly. The main aim of the maven-release plugin is to provide a standard mechanism to release project artifacts outside the immediate development team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |