[
https://jira.jboss.org/browse/JBBUILD-549?page=com.atlassian.jira.plugin....
]
Paul Gier closed JBBUILD-549.
-----------------------------
Assignee: Paul Gier
Fix Version/s: Maven Build Support 2010
Resolution: Done
The wiki contains several options for maintaining versions in the POMs.
http://community.jboss.org/wiki/UpdateMavenProjectVersions
At this point, I'm closing the issue because there isn't anything more that can be
done. This will have to eventually be fixed in upstream Maven.
Redundant version information
-----------------------------
Key: JBBUILD-549
URL:
https://jira.jboss.org/browse/JBBUILD-549
Project: JBoss Build System
Issue Type: Task
Components: Sonatype
Reporter: Paul Gier
Assignee: Paul Gier
Fix For: Maven Build Support 2010
From Max's email:
This comes back to us having a project with a set of modules that we would rather have
the version number be the same
than having to mock with updating pom.xml's (witth or without the release plugin).
Is there a way to avoid having to list and maintain i.e. 3.5.0-SNAPSHOT in *every*
submodule's pom.xml ?
We basically just want maven to pickup the version from the parent pom based on the
filesystem location and not
via the repo. (best way I can explain it ;)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira