[ http://jira.codehaus.org/browse/MNG-624?page=comments#action_66973 ]
Prasad Kashyap commented on MNG-624:
------------------------------------
The Geronimo project has about 145 pom.xmls layered in 3 to 4 tiers.
Ideally, we would like to set the version in one single place and use it
repeatedly everywhere. This would include the version for the <project> and for
the <parent>. Example :
<project>
<parent>
<groupId>org.apache.geronimo</groupId>
<artifactId>geronimo-parent</artifactId>
<version>${geronimoVersion}</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.geronimo.applications</groupId>
<artifactId>applications-parent</artifactId>
<version>${geronimoVersion}</version>
...........
Such a thing is not possible.
If we want to do a top level build with 1 single 'mvn' command, then we cannot
use ${geronimoVersion} while declaring the project's and
parent's version. We will have to explicitly define the version. That would
mean changing every single pom.xml every time the release
changes.
Setting the version in -D doesn't work either.
> automatic parent versioning
> ---------------------------
>
> Key: MNG-624
> URL: http://jira.codehaus.org/browse/MNG-624
> Project: Maven 2
> Type: Improvement
> Components: Inheritence and Interpolation
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.1
>
> Original Estimate: 4 hours
> Remaining: 4 hours
>
> (this may be bumped to 2.1 or even made WON't FIX as it is contentious - see
> MNG-521)
> currently, you have to specify the parent version when extending which makes
> a project stand alone very easily, but has the drawback of being a
> maintainance problem when you start development on a new version. Tools can
> help, but it would be nice not to have to rely on them.
> One alternative is to allow the parent version to be omitted, and when it is
> it is assumed you want the latest. The parent is used from the reactor or the
> universal source directory. IT may also be read from a LATEST in the
> repository though this is contentious - it may be better to simply fail in
> that environment and require builds be in a known checkout structure for
> building individual projects.
> This also introduces the need for tool support to populate the version on
> release and deployment for reproducibility.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
