Hi, Am Dienstag, den 03.06.2008, 15:57 +0200 schrieb Carsten Ziegeler: > Bertrand Delacretaz wrote: > > I agree, but aren't we abusing it already? > > > > We are marking dependencies as "provided", but including them in the > > generated artifact using the maven-bundle-plugin. > > > > The correct scope (although it does not exist, and IIRC you said > > custom scopes pose problems) might be "bundled" in this case, and the > > maven-bundle-plugin would then complain if trying to include the code > > of any package in the bundle code, unless that package comes from a > > "bundled" dependency, or comes from the project itself. > > > Usually I use the scope "compile" when including bundles :) which is > closer as optional and provided to what we do...not optimal though.
The problem with compile is that it creates hard transitive dependencies, which is not what you want when including library code into the bundle. Regards Felix
