[
https://issues.apache.org/jira/browse/FELIX-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188881#comment-15188881
]
Christian Schneider commented on FELIX-5210:
--------------------------------------------
I guess the plugin works out the import packages by parsing the information
from the jar that maven actually selects.
The problem is that to use the packages from the 1.0.0 jar the plugin would
need to first resolve this bundle.
So if you want to achieve compatiblity with the lower versions you have to set
the maven dependency to the lowest version your code should work with.
> maven-bundle-plugin picks too restrictive version
> -------------------------------------------------
>
> Key: FELIX-5210
> URL: https://issues.apache.org/jira/browse/FELIX-5210
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Reporter: Fabian Lange
>
> I am using the maven bundle plugin to build my manifests.
> What I just noticed is that it is too restrictive on versions.
> I have a dependency saying
> {code}
> <version>[1.0.0,2.0.0)</version>
> {code}
> But the bundle plugin (2.5.4 and 3.0.1) generate
> {code}
> ;version="[1.1,2)
> {code}
> while the 1.1 version does exist, my bundle would happily work with 1.0,
> which is also what my maven config says.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
