Re: Maven release:prepare and NOT creating SNAPSHOTs
I was hoping to just cut the release and not create the snapshot for a couple of reasons. I have version 1.0-SNAPSHOT. I'm done developing so I want to create version 1.0, Get that into our mvn repo and update our hg repo. At this point, I do know that I am done with version 10., but I don't know if my next release will be version 2.0, 1.1, or 1.0.1. I'd like to stop the process after it updates the hg repo with the 1.0 version. Once I know what version I will be working on, I'd like to create a branch in hg and create a SNAPSHOT release in mvn. Thanks Neil On Mon, Jun 20, 2011 at 8:11 PM, Barrie Treloar baerr...@gmail.com wrote: On Tue, Jun 21, 2011 at 9:14 AM, Wendy Smoak wsm...@gmail.com wrote: On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart neilah...@gmail.com wrote: I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. Did you try setting developmentVersion? That seems to control the 'next snapshot'. http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the release process without disrupting the developers. Ahh fair enough. I assumed that he would be releasing the non snapshot version, not choosing a new version like your example, which makes sense to do. If this is what he is doing, and he is running release:prepare incrementally you can always just type in the version number you want. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 9:19 AM, Neil Hart neilah...@gmail.com wrote: I was hoping to just cut the release and not create the snapshot for a couple of reasons. I have version 1.0-SNAPSHOT. I'm done developing so I want to create version 1.0, Get that into our mvn repo and update our hg repo. At this point, I do know that I am done with version 10., but I don't know if my next release will be version 2.0, 1.1, or 1.0.1. I'd like to stop the process after it updates the hg repo with the 1.0 version. Well.. you don't want to leave 'trunk' sitting there with a non-snapshot version number. Anyone who checks it out and builds it (CI server perhaps?) will re-create that version in their local repo, (and maybe even try to deploy it) which might not match the real released version, causing all sorts of havoc. If you're not sure what the next version is... set it to TBD-SNAPSHOT or something. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release:prepare and NOT creating SNAPSHOTs
I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. I've tried a few of the properties in the release plugin without success. Do I need to override the maven-release-manager some how? Can this be done? Thanks Neil
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 5:16 AM, Neil Hart neilah...@gmail.com wrote: I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. I've tried a few of the properties in the release plugin without success. Do I need to override the maven-release-manager some how? Can this be done? The next snapshot is just a best guess at the version number. It doesn't really mean anything definite. I'm not sure why you are trying to do this. At release time, or some time later in development you might decide that your change set requires a change in the major or minor version numbers (i.e. its not just a patch update) See http://semver.org/ The best guess that maven-release-plugin uses is the version number (Major.Minor.Patch) upgraded to Patch+1-SNAPSHOT What you DEFINITELY don't want to do is NOT increase the version number. Once you release your artifact it SHALL NEVER CHANGE. If its borked, you need to spin a new release but never override the just released one. If you want to give some sort of QA or sanity check on a release before letting it loose in the wild, then you need to consider a repository manager that uses a staging area. You release to the staging area, the people doing the sanity check pull in from your temporary staging area, do their checks, and once the green light is given the artifact is promoted out of staging into the proper release area. This lets you re-spin with the same version number because you never publicly released the artifact. Hopefully this helps. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart neilah...@gmail.com wrote: I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. Did you try setting developmentVersion? That seems to control the 'next snapshot'. http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the release process without disrupting the developers. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:prepare and NOT creating SNAPSHOTs
On Tue, Jun 21, 2011 at 9:14 AM, Wendy Smoak wsm...@gmail.com wrote: On Mon, Jun 20, 2011 at 3:46 PM, Neil Hart neilah...@gmail.com wrote: I would like to run release:prepare without creating a new development version. I don't always know the next version number when versioning the current build. Later I could run release:branch (perhaps). This is using Maven 2.2.1. Did you try setting developmentVersion? That seems to control the 'next snapshot'. http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html FWIW I think it's a valid request. Sometimes I have 1.0-SNAPSHOT and I release 1.0-test then go back to 1.0-SNAPSHOT. I can test the release process without disrupting the developers. Ahh fair enough. I assumed that he would be releasing the non snapshot version, not choosing a new version like your example, which makes sense to do. If this is what he is doing, and he is running release:prepare incrementally you can always just type in the version number you want. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
