Hi Carsten, I think this case is similar to what we do in the framework subproject. We have dependencies on the org.osgi.core and org.osgi.compendium subprojects and at the same time override some classes from those libraries with our own classes.
So you might want to take a look at our framework/pom.xml. In general, the trick to make it work is to use the unpack task from the maven-dependency-plugin iirc. However, I'm not a maven expert :-) regards, Karl On 7/17/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Hi, we are using the maven bundle plugin (which works great btw) and now face the following problem: Together with our own code we want to bundle a 3rd party library and at the same time override some classes from this library with our own classes (to include some hot fixes and patches). So, basically we have a maven project which has our own code and the patch code in source, a dependency to the 3rd party library and that's it. When building the bundle, it seems that the clases from the 3rd party artifact are preferred and therefore our patches never make it into the bundle. Is there a way of achieving this? Regards Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
-- Karl Pauls [EMAIL PROTECTED]
