On 18/07/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Peter Kriens wrote: > Bnd follows the classpath order as far as I can see. For the maven > plugin I get the classpath from maven. I had a quick look at the source code of bndlib (0.0.160) and from what I saw I have the feeling that if I use for example "export package org.apache.felix.*" and classes for this package are more then once in the classpath, then the later ones overwrite the earlier ones. I hope my analysis is correct (and I don't make a fool of myself) as I think that Jar#putResource() is the method in question and it does not check if a resource already exists. Could this be the problem?
I think so - just been debugging a problem for niclas where a class in target/classes was being overridden by a matching entry from a dependency (both internal classes, not exported). If I modify the putResource method to return if the resource already exists, then this class doesn't get overriden and the correct version appears in the final bundle.
> > Anyway, split packages are a pain in the ... Preventing them and ant > least treating them consciously is always a better idea. > :)
definitely - in this case, the culprit was a leftover class from a refactoring...
Regards Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
-- Cheers, Stuart
