[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-2199:
-------------------------------
Description:
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.
was:
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.
> Version ranges not supported for parent artifacts
> -------------------------------------------------
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
> Affects Versions: 2.0.3
> Reporter: Christian Schulte
> Assignee: Jason van Zyl
> Fix For: Issues to be reviewed for 4.x
>
> 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
>
>
> 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.1.6#6162)
