[
http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190889#action_190889
]
Todor Boev commented on MNG-2199:
---------------------------------
I think there is an acceptable alternative: Make <relativePath> pick up the
maven coordinates of the parent pom automatically.
Most multi-module builds form a monolithic tree of poms that is always checked
out atomically. I.e. we have a specific tree layout in the file system that has
<module> for forwards links and <parent> for backlinks. If <module> does not
need full maven coordinates why should parent? Imagine we can use either maven
coordinates or a single <relativePath> as parent:
<parent>
<relativePath>../pom.xml</relativePath>
</parent>
Than the entire multi-module project can have a single groupId and version set
in the root pom. We would be able to control the common version of this
logical set of artifacts from one file - no more need to edit dozens of
<parent> clauses for every trivial change. All that is needed is for Maven to
replace <relativePath> with the actual maven coordinates when we install/deploy.
For that matter why don't we make <module> accept a set of maven coordinates as
well? Than both the forward and backward links would support two modes: maven
coordinates and the repo or local file system and automatic maven coordinate
interpolation upon install/deploy.
> Version ranges not supported for parent artifacts
> -------------------------------------------------
>
> Key: MNG-2199
> URL: http://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation, POM, Reactor and workspace
> Affects Versions: 2.0.3
> Reporter: Christian Schulte
> Fix For: 3.x
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
> <parent>
> <artifactId>artifactId</artifactId>
> <groupId>groupId</groupId>
> <version>[2.0, 2.0.1]</version>
> </parent>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
> <parent>
> <artifactId>artifactId</artifactId>
> <groupId>groupId</groupId>
> <version>[2.0, ${pom.version}]</version>
> </parent>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
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
