You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Christoph Höger (JIRA)" <ji...@codehaus.org> on 2010/08/02 12:35:32 UTC

[jira] Created: (MECLIPSE-666) eclipse:install-plugins misinterprets Require-Bundle version

eclipse:install-plugins misinterprets Require-Bundle version
------------------------------------------------------------

                 Key: MECLIPSE-666
                 URL: http://jira.codehaus.org/browse/MECLIPSE-666
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: OSGi, Manifest
    Affects Versions: 2.8
         Environment: Fedora 13, maven 2.0.8
            Reporter: Christoph Höger


>From section 3.2.6 of the OSGi specification it follows that a version range consisting of only a single version should be interpreted as "at least":

> If a version range is specified as a single version, it must be interpreted as the
> range [version,&#8734;)

Despite of this the eclipse plugin creates pom files with exact dependencies. For an example see the org.eclipse.equinox.p2.engine plugin. It has the line 

Require-Bundle: org.eclipse.equinox.common,org.eclipse.equinox.registr
y,org.eclipse.osgi,org.eclipse.equinox.p2.metadata.repository;bundle-version="1.0.100",org.eclipse.core.jobs;bundle-version="[3.4.0,4.0.0)
" 

The created org.eclipse.equinox.p2.engine-1.0.102.pom contains:

      <groupId>org.eclipse.equinox</groupId>
      <artifactId>org.eclipse.equinox.p2.metadata.repository</artifactId>
      <version>1.0.100</version>

Although this dependency cannot be resolved (metadata.repository is installed in version 1.0.101).


-- 
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