[
https://issues.apache.org/jira/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286157#comment-16286157
]
Hudson commented on MNG-2199:
-----------------------------
Build unstable in Jenkins: Maven TLP (wip) » maven » pre-reset-master #3
See https://builds.apache.org/job/maven-wip/job/maven/job/pre-reset-master/3/
> Support version ranges in parent elements
> -----------------------------------------
>
> Key: MNG-2199
> URL: https://issues.apache.org/jira/browse/MNG-2199
> Project: Maven
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
> Affects Versions: 2.0.3
> Reporter: Christian Schulte
> Assignee: Christian Schulte
> Fix For: 3.5.0-alpha-1, 3.5.0
>
> Attachments: MNG-2199-3.0.4.patch, MNG-2199-3.0.4.patch,
> MNG-2199-3.1.0-alpha-1.patch, MNG-2199.patch, MNG-2199.patch, MNG-2199.patch,
> MNG-2199.patch, MNG-2199.patch, MNG-2199.patch, test-project.zip
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
> {code:xml} <parent>
> <artifactId>artifactId</artifactId>
> <groupId>groupId</groupId>
> <version>[2.0, 2.0.1]</version>
> </parent>{code}
> {noformat}[INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom{noformat}
> Additionally it would be great if this
> {code:xml} <parent>
> <artifactId>artifactId</artifactId>
> <groupId>groupId</groupId>
> <version>[2.0, ${pom.version}]</version>
> </parent>{code}
> {noformat}[INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom{noformat}
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
