[
https://issues.apache.org/jira/browse/ARIES-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003920#comment-13003920
]
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(LoggerFactory.java:230)
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248)
at org.apache.aries.jndi.startup.Activator.<clinit>(Activator.java:56)
at
org.apache.aries.jndi.InitialContextTest.setup(InitialContextTest.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
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: https://issues.apache.org/jira/browse/ARIES-599
> 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] http://markmail.org/message/hzwtvpqijt6tdnia
> [2]
> http://svn.apache.org/repos/asf/aries/trunk/jndi/jndi-core/src/main/java/org/apache/aries/jndi/startup/Activator.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
