maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joost den Boer (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts
Date Mon, 01 Feb 2010 14:07:56 GMT

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

Joost den Boer commented on MNG-2199:
-------------------------------------

Don't agree with Todor. Using relative path is not a solution since lots of projects have
a (company wide) parent pom but are not part of a multi-module project.
As Sylvain said version ranges would be very handy when changing release configuration, license,
etc and those are exactly the kind of things you want to configure globally for all company
projects. All clients I have worked for have their own main pom in which they define this
kind of things. Now, when a new version of that main pom is released, it's a nightmare to
change all poms that use it directly and indirectly.

So for me a +1 for this issue.

> 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: 3.x (to be reviewed)
>
>
> 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

        

Mime
View raw message