[jira] (MECLIPSE-373) eclipse:to-maven cannot resolve Required-Bundle: system.bundle

["Christian K. (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MECLIPSE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346274#comment-346274 ] 

Christian K. commented on MECLIPSE-373:
---------------------------------------

Patching the to-maven mojo would be quite simple adding something like
{code}
if(dep.getGroupId().equals("system") && dep.getArtifactId().equals("bundle"))
{
	// skip special OSGI system bundle dependency
	continue;
}
{code}
to org.apache.maven.plugin.eclipse.EclipseToMavenMojo.createModel(EclipseOsgiPlugin) would be sufficient. If a maintainer is avaialbel for integration I would be happy to prepare a patch (also for MECLIPSE-719).

> eclipse:to-maven cannot resolve Required-Bundle: system.bundle
> --------------------------------------------------------------
>
>                 Key: MECLIPSE-373
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-373
>             Project: Maven Eclipse Plugin
>          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
>
> 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.1.6#6162)