The version policy is not implemented in the maven plugin. This should happen soon because Stuart McCulloch was telling me he was going to work on this.

Kind regards,

        Peter Kriens

On 2 dec 2008, at 14:20, Hampel, Michael wrote:

Hello,

I have a question about how bnd determines the version for an
import-package.
(I am using the maven bundle plugin version 1.4.3).
I have the following behaviour:

If I export packages with the version 1.0.25 then bnd imports these
packages with version 1.0.
(I think this is conform to the documentation - "though the micro part
and the qualifier are dropped")

If I export packages with the version 1.0.25.0 or 1.0.25.SNAPSHOT then
bnd imports these packages with
version  1.0.25.0 or 1.0.25.SNAPSHOT.
(which I think is not conform to the documentation?)

As in the end I want to have import version 1.0.25 I tried out the
-versionpolicy option like this
(in the maven bundle plugin)
<Import-Package>*;-versionpolicy:[EMAIL PROTECTED]</Import-Package>

but this did not work either (still get version 1.0) - but maybe I am
using this policy in the wrong way.

Can someone please advise how I get version 1.0.25 for imported
packages?

Thanx in advance for any help,

Michael




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to