You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Michaelis (JIRA)" <ji...@codehaus.org> on 2010/06/10 10:11:12 UTC

[jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts

    [ http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224811#action_224811 ] 

Mark Michaelis commented on MNG-2199:
-------------------------------------

We also need this issue to be resolved - actually MNG-624 (no version = use latest parent) is not enough from my point of view. We need this parent POM for environmental settings (where are repositories and such) which always needs to be up to date. But: We also need to build old projects with this parent POM - and to allow to refactor the property names for example some day we need to have a rule like: In each major version of the parent POM its "API" (i. e.: the property names) stay the same.

Up to now we used settings.xml for this which we handed over through the invoker-plugin. The settings.xml were downloaded and unpacked as dependency - which of course supports version ranges. But the invoker-plugin poses other problems so that it is not a solution for us anylonger.

> Version ranges not supported for parent artifacts
> -------------------------------------------------
>
>                 Key: MNG-2199
>                 URL: http://jira.codehaus.org/browse/MNG-2199
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Inheritance and Interpolation, POM, Reactor and workspace
>    Affects Versions: 2.0.3
>            Reporter: Christian Schulte
>             Fix For: Issues to be reviewed 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