Hi Rémy, I don't have an answer for you, but I just wanted to make a couple of points.
* you only run the release plugin on a snapshot version * normally, a snapshot will be on the trunk or a branch * release:prepare creates a tag with the non-snapshot version, which is the "released code" * if you then had the situation where you *didn't* move the version numbers on, you would have a non-snapshot version on the trunk or a branch. This scenario makes it possible to have multiple builds of the same version number with different code in it. If these were deployed to a shared maven repository, there is no indication which one you are looking at. Having snapshot in the version makes it very clear that it is in a transient state, and not released code. Maybe if you explain why you want to do this, I can be of more help. cheers, Craig On Tue, Oct 28, 2008 at 10:25 AM, Rémy <[EMAIL PROTECTED]> wrote: > > I use the maven-release-plugin, the two goals prepare and perform. But I > don't want Maven generate the pom for the next iteration how can I do that ? > I want simply to pass from the snapshots to the releases. > Thanks. > Rémy. > -- > View this message in context: > http://www.nabble.com/maven-release-plugin-tp20198588p20198588.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
