On Wed, Sep 24, 2008 at 4:33 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> 2008/9/24 Niclas Hedhman <[EMAIL PROTECTED]> > >> >> On Wed, Sep 24, 2008 at 12:06 PM, David Leangen <[EMAIL PROTECTED]>wrote: >> >> >>> So, to correct what I want to do: I want to _import_ that package. ;-) >>> >>> My goal is to get access to the org.apache.logj4.net package, which is >>> not available at runtime because that package is not embedded into the >>> pax-logging-service bundle. >>> >> >> Uhhhhhh.... I think you have stumbled upon another bug. >> >> Perhaps Stuart can help out here; The Maven Bundle Plugin is apparently >> now inlining the packages into the built Jar. This is different from >> previous behavior when the Log4j jar file was included in full and placed on >> the internal bundle classpath. >> > > well, it only does what's it is told to :) so if you want it to embed log4j > rather than inline then it's just a matter of setting the right > instructions > > >> Originally, the entire Log4j was internally available, and the >> Private-Package was there to direct BND to do the right thing. >> > > would you prefer log4j embedded or inlined? > Well, from the beginning Jar files got stored in the Bundle jar... Somewhere along the line that behavior changed, and not sure when, possibly ages ago. Point is, it was never detected... I think I don't really care, as long as BND can be instructed not to care about the optional stuff and com.sun stuff in some packages and still have the included. Cheers Niclas
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
