If you can send the culprit to me then I will have a look.
It sounds a bit odd, a missing uses directive should not end up in Class Def
Not Found error, worst case you could get a class cast exception. Uses are only
important for systems that have multiple versions of the same package.
It is not very likely that 1.43.0 is improving such a situation, no changes
have been made in this area.
Kind regards,
Peter Kriens
On 14 apr 2011, at 08:55, Yuri de Wit wrote:
> I noticed that the current 2.3.4 maven-bundle-plugin has a dependency
> on an older version of bndlib 1.15.0. Is there a snapshot somewhere
> with the latest 1.43.0? Where are the sources for the
> maven-bundle-plugin?
>
> The main reason I am interested in this is that I am having a strange
> issue where a "uses"directive is not being generated in the
> Import-Package/Export-Package for a specific package and I end up
> getting a NoClassDefFoundError when activating the module in felix. I
> have X and Y modules that depend on A module. The A module has an
> interface A that extends another interface b.B . The X interface in
> module X extends A and so does the Y interface in the module X. For
> some strange reason the X module has the uses=b, but the module Y
> doenst.
>
> I hacked the Manifest to include the missing package in the uses
> directive and it seems to have worked. So the question is why would
> maven-bundle-plugin not generate the b package in the uses directive
> for the Y module?
>
> ---------------------------------------------------------------------
> 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]
