Having 'mvn deploy' in Hudson's build goals and the standard approach of releasing

Posted by user68759 on Stack Overflow See other posts from Stack Overflow or by user68759
Published on 2010-12-24T01:44:06Z Indexed on 2010/12/24 2:53 UTC
Read the original article Hit count: 238

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

One thing I have been wondering is whether I should include deploy in the build goals because it could happen that if I had just released version 1.0.0 of my project (I've changed the pom to be version 1.0.0 and committed it) but not yet increased the version number to 1.0.1-SNAPSHOT for several days, I could end up with multiple different 1.0.0 builds being deployed at different times.

But I've seen people are using deploy in their Hudson's build goals - I wonder how they deal with this issue.

What's the correct way of doing a release with Maven actually? Thanks for any pointers!

© Stack Overflow or respective owner

Related posts about java

Related posts about maven-2