Not sure about the details in this case, but in principle; a. Do not include any logging APIs inside your bundle. b. Do not try to deploy any logging APIs as bundles on the OSGi framework. c. Import-Package the relevant logging APIs in your bundles that needs it. d. Deploy Pax Logging as the logging API and logging back end solution.
In nearly all cases you will be fine. If you only use SLF4J it is practically certain you will be ok. I am not competent in Pax Exam to know if it has any nasty tricks up its sleeve for that not to work, but I assume not. Cheers Niclas On Tue, Jun 21, 2011 at 4:17 AM, Sanjeeb Sahoo <www.sa...@gmail.com> wrote: > Sorry, I was wrong when I said the probe bundle embeded slf4j api. > It's the pax-exam-extender-service bundle which is bundling the slf4j > api jar. How am I supposed to supply an slf4j binding to it? Is there > a fragment bundle made available in pax-exam project that I can attach > to the pax-exam-extender-service bundle? > > Sahoo > On Tue, Jun 21, 2011 at 12:31 AM, Sanjeeb Sahoo <www.sa...@gmail.com> wrote: >> >> I see the probe bundle actually embeds slf4j api jar. How can I make >> it embed an implementation as well so that I can avoid the NCDFE? > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
