You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:32:12 UTC
[jira] (MECLIPSE-302) resolveVersionRanges crashes on system.bundle
[ https://jira.codehaus.org/browse/MECLIPSE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MECLIPSE-302.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> resolveVersionRanges crashes on system.bundle
> ---------------------------------------------
>
> Key: MECLIPSE-302
> URL: https://jira.codehaus.org/browse/MECLIPSE-302
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Affects Versions: 2.4
> Reporter: Matthew Beermann
> Attachments: MECLIPSE-302-maven-eclipse-plugin.patch, MECLIPSE-302-maven-eclipse-plugin.patch
>
>
> When running eclipse:make-artifacts with -DresolveVersionRanges=true, it dies with the following error:
> [INFO] Unable to resolve version range for dependency Dependency {groupId=system.bundle, artifactId=system.bundle, version=[0,), type=jar} in project org.apache.xml.org.apache.xml.resolver
> It turns out that "system.bundle" is a keyword in OSGi that (broadly speaking) refers to the JRE itself, and thus need not/should not be included in the POM as a dependency. I've got a patch for this coming up in a moment.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)