[
https://jira.codehaus.org/browse/MECLIPSE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-666.
-----------------------------------
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.
> eclipse:install-plugins misinterprets Require-Bundle version
> ------------------------------------------------------------
>
> Key: MECLIPSE-666
> URL: https://jira.codehaus.org/browse/MECLIPSE-666
> Project: Maven 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,∞)
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
