aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (JIRA)" <>
Subject [jira] Commented: (ARIES-599) Consistently use SLF4J Logging
Date Tue, 08 Mar 2011 13:00:59 GMT


Alasdair Nottingham commented on ARIES-599:

Applying the provided patch causes the tests to fail with the following exception:

java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
	at org.slf4j.LoggerFactory.getSingleton(
	at org.slf4j.LoggerFactory.bind(
	at org.slf4j.LoggerFactory.performInitialization(
	at org.slf4j.LoggerFactory.getILoggerFactory(
	at org.slf4j.LoggerFactory.getLogger(
	at org.apache.aries.jndi.startup.Activator.<clinit>(
	at org.apache.aries.jndi.InitialContextTest.setup(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(

I suspect this is because we have the slf4j api, but not the impl in the pom.

> Consistently use SLF4J Logging
> ------------------------------
>                 Key: ARIES-599
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Felix Meschberger
>         Attachments: ARIES-599.patch
> It looks like certain classes are not using SLF4J API as should be done according to
Alasdair Nottingham [1].
> One such example is the JNDI Core BundleActivator [2]. Will search for others and try
to provide a patch.
> [1]
> [2]

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message