versions:set changes the version of the module you run it in. the then
jumps up the directory tree as long as you have aggregator projects,
and then updates all references to the old version to be the new
version, including updating child pom's that inherit the version
Sent from my [rhymes with myPod] ;-)
On 28 May 2009, at 23:09, Joerg Hohwiller <[email protected]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
and mvn versions:set -DnewVersion=_____ is already implemented in
trunk
for 1.0-beta-1
mhm, I do not know if that is exactly what I am looking for.
Can I specify the artifactId and or groupId so such module
in my reactor will be changed in version if present as well
as all matching dependencies of all modules are changed?
To me the versions-maven-plugin looked quite complicated
and seems to have a different intention.
Sorry for my ignorance but I already started implementing
a new MOJO (pom-maven-plugin) that can do general
refactorings of POMs (but does NOT look in repositories
for what version is available, etc.) and it just starts
working :)
If I can solve my problems with your plugin,
then I will immediately drop my work. Otherwise I'd
suggest to commit to sandbox and you can take all ideas
and code you want and migrate it into versions-maven-plugin
or we see that these are two different animals here
and they should co-exist...
Regards
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkofC5oACgkQmPuec2Dcv/+aZwCeJgdaxCGLifY1Zd+TUwDxasib
LP8An1WdK1OoE2fGz+3k08bh3IABkmee
=3FLj
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
