Geek asks and answers

Maven release from Tagged Release Candidate or Branch

Consider the following scenario: I have a project that is being developed using mavenas a build tool and svnor another version control tool.

At some point, I decided that it was "probably" ready for release, and I set the tag svnto mark it asrelease candidate

+ Trunk (0.0.1-SNAPSHOT)
|
+----------------------------+ Branch "release-candidate" (0.0.1-SNAPSHOT)
|                            | (goes to QA for testing)
+ Trunk (0.0.2-SNAPSHOT)     | 
| (development continues)    + Tag "release-0.0.1" (0.0.1)
....                           (deploy this revision)

At this point, I need to upgrade pom.xmlwith a new version of development. release-candidatesaves the snapshot version until the QA is completed with testing and announces readiness for release. Only then the actual deployment + deployment will be performed on the tag / branch.

Development can continue in the trunk while a release candidate is being tested.

Is it possible to implement this two-step script using the maven build? Is there enough plugin releasefor this or do I need others?

+3
source share
1 answer

Maven Release Plugin is the de facto standard for releasing Maven projects, and for this it creates a specific workflow. As I can see, you have quite different assumptions, but if you try to fit into the Maven convention here, the Maven Release Plugin will do everything here.

, release:branch , bumping trunk . , , (release-candidate ) . , , . , 0.0.1, , . , , release:branch <scm /> POM, , - - .

, release:prepare release:perform , Maven. , ..

, , (- - ), svn:externals release-candidate, .

+3

More articles:


All Articles