If you require that functionality you will need to downgrade to an earlier version (I think 0.7.1).
The functionality will be coming back but I have no current ETA. See https://issues.jenkins-ci.org/browse/JENKINS-11466 /James From: [email protected] [mailto:[email protected]] On Behalf Of Hilikus Sent: 17 May 2013 16:50 To: [email protected] Subject: m2 release plugin versioning policy Hello everyone, It looks like the current behaviour when doing a maven release from jenkins in a multi-module project is to assign the version specified in the web ui of jenkins to ALL the submodules e.g in a project like this 1.0.0-SNAPSHOT (A) |...1.0.0-SNAPSHOT (A1) |...2.3.0-SNAPSHOT (A2) if I specify in the ui that the version of the root pom (A in my example) should be 1.0.0 then even the second submodule (2.3.0-SNAPSHOT) will be released with version 1.0.0, probably due to the -B -DreleaseVersion arguments combo. Is there any way to change this behaviour? what I want is to release A1=1.0.0, A2=1.0.0 and A3=2.3.0 I see a "default versioning mode" in the configuration that seems to do just that; however, 1) it never keeps its state, whatever I change it to, it goes back to none 2) it doesn't even look like the actual behaviour is none, since none seems to be what I want. The behaviour I see is "specify one version for all modules" I'm using m2release 0.10 and jenkins 1.460 Thank you -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
