Hello,
I just submitted a patch for this bug:
http://jira.codehaus.org/browse/MNG-3559
I don't know if it is the 'correct' fix, but it does the job for my
issue.
Unfortunately, I can't want for a new Maven release, so I need to
build an in-house version with this patch to deploy to my development
team. I'm building off the maven 2.0.9 tag, and tried tweaking the top
level pom's version to be 2.0.9.1 and that didn't seem to work (mvn
package still built 2.0.9).
How would I change the Maven version number?
Is there a best practice for naming an in house version? I was
thinking of something like 2.0.9-kiva-1.
Last question: Is there any way I can ease deployment of this version
via our shared in-house repository? If it was a plugin I would just
upload it into the repo and change our project's dependency, but in
this case its Maven it self. I think I need everyone to download the
tar.bz or zip and install it, right?
Thanks,
Josh
--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
