So this is a known bug or is it just a configuration error that I did? I have to specify all versions of each module of my reactor? Or it can take the basic version-DreleaseVersion for each module?
-----Message d'origine----- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : mardi 23 juillet 2013 10:10 À : Maven Users List Objet : AW: mvn release:prepare does not update parent version Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-inte ractive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -----Ursprüngliche Nachricht----- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg <k...@quipsy.de> wrote: > When I do mvn release:prepare, Maven asks whether I want to update all > SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? > I say "yes" and confirm all suggested replacement versions unchanged. > When Maven is done, I check the POM.xml. > It is correctly rewritten for all references, but not for the parent > version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. > The parent version still references the *old* SNAPSHOT, while > obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. > Can somebody tell me what I have to do so that mvn release:prepare > will also make the parent version point tot he *next* SNAPSHOT, as it > does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
