Pax Exam 2 artifacts do not embed slf4j api, can you give a pointer that
leads to the evidence ?
Instead, we do install some infrastructure bundles into the system.
Those are:
url( "link:classpath:META-INF/links/org.ops4j.pax.exam.rbc.link"
).startLevel( START_LEVEL_SYSTEM_BUNDLES ),
url( "link:classpath:META-INF/links/org.ops4j.pax.extender.service.link"
).startLevel( START_LEVEL_SYSTEM_BUNDLES ),
url( "link:classpath:META-INF/links/org.osgi.compendium.link" ).startLevel(
START_LEVEL_SYSTEM_BUNDLES ),
url( "link:classpath:META-INF/links/org.ops4j.pax.logging.api.link"
).startLevel( START_LEVEL_SYSTEM_BUNDLES ) };

As you see, pax logging api gets installed by default. You cannot change
that currently (Pax Exam <= 2.1.0 )

On Sun, Jul 3, 2011 at 6:58 PM, Sanjeeb Sahoo <[email protected]> wrote:

> Pl. update this thread with your findings...
>
> Thanks,
> Sahoo
>
> On Wed, Jun 29, 2011 at 9:03 AM, Sanjeeb Sahoo <[email protected]>
> wrote:
> > any thoughts on this subject?
> >
> > On Wed, Jun 22, 2011 at 12:57 AM, Toni Menzel <[email protected]>
> wrote:
> >> I will have a look at this in the evening.
> >> I need to check what the exam-extender service relationship to slf4j was
> >> like. I recall some solution that benefits exam tests with any foreign
> (or
> >> none)  slf4j/paxlogging.
> >>
> >> On Tue, Jun 21, 2011 at 7:49 PM, Niclas Hedhman <[email protected]>
> wrote:
> >>>
> >>> 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 <[email protected]>
> >>> 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 <[email protected]
> >
> >>> > 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
> >>> > [email protected]
> >>> > 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
> >>> [email protected]
> >>> http://lists.ops4j.org/mailman/listinfo/general
> >>
> >>
> >>
> >> --
> >> Toni Menzel Source
> >>
> >>
> >> _______________________________________________
> >> general mailing list
> >> [email protected]
> >> http://lists.ops4j.org/mailman/listinfo/general
> >>
> >>
> >
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
>



-- 
Toni Menzel Source <http://tonimenzel.com>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to