On 10/26/10 3:08, Peter Kriens wrote:
I think this is a framework error :-) The parts of the versions are integers this
04 == 4. So 0.04.0.SNAPSHOT>= 0.4
Yeah, actually, that didn't even dawn on me. How/when are you getting an
unresolved constraint?
-> richard
But I can add a feature to bnd to cleanup the import version. I am already
doing this for getting rid of the - sign and other mavenisms.
Kind regards,
Peter Kriens
On 22 okt 2010, at 22:48, [email protected] wrote:
All,
A project I'm working with is using a very minimalist implementation of the maven
bundle plugin that relies on the maven-bundle-plugin to use the default version of
the bundle for<Bundle-Version>(whatever the pom.version property is set to).
In this case, the version is 0.04-SNAPSHOT.
In the Export-Package section of the MANIFEST.MF file, the number is resolved to
"0.04.0.SNAPSHOT", which is the expected behavior.
In the Import-Package section of the MANIFEST.MF file, all of the bundles packages are
imported with version "0.4". This creates an unresolved constraint violation
upon deployment.
I have spoken with the project, and they will be using "0.4-SNAPSHOT" as thier
pom.version. However, this is a workaround, and there still appears to be a bug in the
plugin or in the BND library.
v/r,
Mike Van
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
