felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-2972) Treatment of version ranges seems incorrect.
Date Wed, 25 May 2011 06:03:48 GMT

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

Andy Jefferson updated FELIX-2972:

    Attachment: bundle_test.zip

Sample maven project that has the issue. Just run "mvn clean install"

> Treatment of version ranges seems incorrect.
> --------------------------------------------
>                 Key: FELIX-2972
>                 URL: https://issues.apache.org/jira/browse/FELIX-2972
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.4
>            Reporter: Andy Jefferson
>         Attachments: bundle_test.zip
> I have a sample project which specifies a dependency on 
>         <dependency>
>             <groupId>javax.jdo</groupId>
>             <artifactId>jdo-api</artifactId>
>             <version>[3.0, )</version>
>             <scope>provided</scope>
>         </dependency>
> and there is a version 3.0, 3.1-SNAPSHOT-20110319, 3.1-SNAPSHOT-20110223 in the specified
> I generate the MANIFEST.MF and it gives an ImportPackage of
> Import-Package: javax.jdo;version="[3.1,4)", ...
> It seemingly just grabs the latest current version available in the repositories in that
range and takes that as the OSGi start version. This is incorrect, since a user could have
v3.0 on their system and deploy that into OSGi and it doesn't allow deployment of this project.
Or is it doing something deeper?

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message