This is just how m2 works... I agree it kinda blows... but bring it
up with the Maven guys, nothing we can do about it at the moment.
The release plugin takes the pain out of having to update every pom's
parent version number... er well it makes it less painful really, but
its manageable pain.
Else any decent search-replace'ing editor can do the bulk of the
dirty work. But I'd use the release plugin when you can.
--jason
On Jul 25, 2006, at 10:50 AM, Aaron Mulder wrote:
One comment for later (post-merge)...
It would be great if we could avoid putting the Geronimo version
number in every POM in every directory throughout the project (in the
<parent> element). I gather there's a chicken-and-egg problem here
(how do you find the parent using the version if the parent defines
the version), but if there was any workaround (trust the relativePath
over the group/artifact/version?), it would be really helpful for the
process of updating a particular location (trunk/branch/tag) to a new
version number.
Thanks,
Aaron
On 7/23/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Please see this issue for details:
http://issues.apache.org/jira/browse/GERONIMO-2219
* * *
I hope to be able to merge this work to trunk in a week or so, so
please, please, please take some time to review the branch and vote
(PMC or not).
--jason
