Alin Dreghiciu wrote:
I'm talking about the package version. I'm going now by a revision of all
wrappings I made and I want also to add the version to the exported
package.
I figured, but we will still need to address the potential incorrect
approach below for existing POM files:
I just looked at commons-collections and (assuming that I am reading the
pom correctly) I think it may have been done incorrectly. It has the
overall bundle-version as 3.2 (i.e., it has <version>3.2</version>), but
doesn't appear to attach any version to the packages. So, ultimately,
this means that you would have an exported package that looked like
this:
Export-Package: foo; version=0.0.0; bundle-version=3.2.0
This is not what we want. We want to version our bundles according to
their degree own version history, so for example our first attempt might
be "0.8.0" or something, but the exported packages are whatever the
original developer says they are. So for commons-collections, we really
want to set <version>0.8.0</version> and tell BND to export with
version=3.2.0. Thus, we would end up with exports like:
Export-Package: foo; version=3.2.0; bundle-version=0.8.0
