Hello, If there's a solution for bnd to determine the version range, then that sounds like the solution I'm looking for. However, I can't see how to do this... I use BND in two ways, either at the command line with a ".bnd" file, and using the Ant task. The only way I can see to set the classpath is for the class files that I want BND to pull into the output JAR. After reading various sources (including "osgibook_preview_20091217.pdf"), I was under the impression that BND determines the imports by inspecting the bytecode of the classes that make up the bundle, and doesn't actually require (or have any way of specifying) the packages and JAR files referred to.
So I can't see how to tell it to inspect other JAR files to extract the version of different Export-Package headers. Could you point me to an example of how I can make a ".bnd" file and the Ant task add versioning information to the Import-Package header without me actually specifying it? Thanks, Christopher On 2 November 2012 23:06, Neil Bartlett <[email protected]> wrote: > For the version issue, it's best if you can build your bundle against > other bundles that have versioned exports. If you do this then bnd will > automatically apply Semantic Versioning rules to set the correct import > range. >
