On Tue, Jun 3, 2008 at 3:29 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: >> On Tue, Jun 3, 2008 at 3:07 PM, Felix Meschberger <[EMAIL PROTECTED]> >> wrote: >>> ...One solution I could see is, that we >>> mark all dependencies, which are included in a bundle as optional....
> Sorry, but I think we are abusing the maven dependency mechanism here a > little bit. If this deps are included in the bundle they are not optional. > So marking them optional just to get a correct notice file seems to be > wrong... 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. -Bertrand
