Right now it doesn't look like bundlor (either in STS or the bundlor mavne plugin) will read the maven dependency versions and scope to augment the imports it will throw into the MANIFEST.MF. (Right?)
Does it make sense that if that information was available it would do so? Ideally it could grab version ranges and look at the dependency scope to see if the dependency was optional and modify the import in MANFEST.MF for things coming out of there to be of the version range and possibly optional.
I'm sure this would get very complicated if/when multiple dependencies might supply the same package, and I'm sure there are other issues I've not thought of yet in my 10 mins of dreaming.
But is this a viable story to enter into JIRA?
"As a developer using maven (in both STS and from the command line), I want Bundlor to tack on version ranges and the optional flag to my MANIFEST.MF package imports from the version ranges and scope supplied by the maven dependency from which the package comes."