[ 
https://issues.apache.org/jira/browse/MECLIPSE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MECLIPSE-373.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

The Apache Maven team has decided to retire the maven-eclipse-plugin, so this 
issue won't be fixed. 


> eclipse:to-maven cannot resolve Required-Bundle: system.bundle
> --------------------------------------------------------------
>
>                 Key: MECLIPSE-373
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-373
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: Bug
>          Components: OSGi, Manifest, PDE support
>    Affects Versions: 2.4, 2.5
>         Environment: Observed under MS Windows XP, probably affects all 
> environments
>            Reporter: Immo Huneke
>            Assignee: Robert Scholte
>
> Install vanilla download of Eclipse RCP Developer (version 3.3.1.1, Europa). 
> Try to install its plugins into the local Maven repository using
> mvn -DeclipseDir="/path/to/eclipse" eclipse:to-maven
> The error you get is:
> {code}[INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Unable to resolve version range for dependency Dependency 
> {groupId=system
> , artifactId=bundle, version=[0,), type=jar} in project org.apache.xerces
> [INFO] 
> ------------------------------------------------------------------------{code}
> My investigations have established that this can be worked around by (a) 
> creating a Maven artifact called "system.bundle" using file:deploy-file, and 
> (b) altering the manifest file to add the specific version number of that 
> artifact to the above bundle requirement. You have to do this for every 
> single Eclipse plugin that has a dependency on the OSGi system bundle. This 
> is very laborious!
> I tried expressing the version number in the manifest as a range, but that 
> didn't work. In other cases, where a version range is required, it seems to 
> work fine, but not for system.bundle. See my blog at 
> http://aspsp.blogspot.com/ for more details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to