Geek Answers Handbook

Having "mvn deploy" in order to build Hudson and a standard release approach

I set up Hudson for my project with build goals mvn clean deploy site:site, run the build every midnight, and whenever new changes appeared.

One thing I was wondering about should I include deployin the build goals, because it could happen that if I just released version 1.0.0 of my project (I changed pom to be version 1.0. 0 and fixed it) , but have not yet increased the version number to 1.0.1-SNAPSHOT in a few days, I could eventually deploy different versions of 1.0.0 at different times.

But I saw how people use the deployHudson building for their own purposes - I wonder how they deal with this problem.

What is the right way to actually make a release with Maven? Thanks for any pointers!

+5
source share
1 answer

You should continue the automatic nightly deployment from Hudson, but the big issue with handling version and release numbers is inextricably linked to your source code management system. You have not mentioned which source control system you are using, but I can explain how to do this with Subversion.

-, , , -, (, -SNAPSHOT ). . , () , , , , , , , , , .

, , Maven Release Plugin , Maven SCM Plugin, .

Maven Release Plugin Hudson, . :

  • , , . , Subversion Nexus .
  • maven-scm-, , , . , , .
  • , : , . , svn .
  • : pom.xml SNAPSHOT. , POM "SNAPSHOT".
  • : URL- SCM . - , , "" .
  • Subversion, maven-release {{suppressCommitBeforeTag}} , trunk pom.xml .

, Maven Hudson, Maven Hudson, , , .

, :

  • SNAPSHOTS
  • Maven .

, .

+9

More articles:


All Articles