[ https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schulte updated MNG-2199: ----------------------------------- Attachment: MNG-2199-3.0.4.patch Patch for Maven 3.0.4. > 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 > Fix For: Issues to be reviewed for 3.x > > Attachments: MNG-2199-3.0.4.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. > <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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira