Resolution: Not a Problem
Affects Version/s: maven-bundle-plugin-2.3.4
Fix Version/s: None
Component/s: Maven Bundle Plugin
I have a sample project which specifies a dependency on
and there is a version 3.0, 3.1-SNAPSHOT-20110319, 3.1-SNAPSHOT-20110223 in the specified respositories.
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?