[ http://jira.codehaus.org/browse/MECLIPSE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-465: ------------------------------------- Affects Version/s: (was: 2.5.2) 2.5.1 > to-maven: extending dependency version-ranges by ".0" > ----------------------------------------------------- > > Key: MECLIPSE-465 > URL: http://jira.codehaus.org/browse/MECLIPSE-465 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Affects Versions: 2.5.1 > Reporter: Lars Fischer > Assignee: Carlos Sanchez > Priority: Minor > > Deploying plug-ins into a maven-repository using "to-maven" generates the > matching dependency-ranges. > Resolving the deployed plugins as dependencies cause problems, if they have > version-numbers with a "-" delimeter and an qualifier-number. > An example: > One eclipse-plugin has a dependency to > <dependency> > <groupId>org.eclipse.core</groupId> > <artifactId>expressions</artifactId> > <version>[3.3.0,4.0.0)</version> > </dependency> > This dependent artefact is deployed as: > <groupId>org.eclipse.core</groupId> > <artifactId>expressions</artifactId> > <version>3.3.0-v20070606-0010</version> > But it is not recognised as a matching artifact. > This could be solved, if the generated dependency range will be changed > from > <version>[3.3.0,4.0.0)</version> > to > <version>[3.3.0.0,4.0.0)</version> > With the additional ".0", maven can resolve the dependency. > Could this be an improvement? > regards, > Lars -- 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