[
https://issues.jboss.org/browse/JBLOGGING-114?page=com.atlassian.jira.plu...
]
Steve Ebersole commented on JBLOGGING-114:
------------------------------------------
I will have more information today. Brett is helping me debug the Karaf issues. JBoss
Logging is not the only one. Quite a few WIldFly jars have problems. The plan is to
follow up with an email to wildfly-dev regarding all of them. The others I know for sure
are all the wildfly "spec" jars (aside from JPA, of course :). Moving to the
geronimo jars fix the issues there. Anyway, will keep you updated. Thanks!
jboss-logging's OSGi metadata is somehow wrong
----------------------------------------------
Key: JBLOGGING-114
URL:
https://issues.jboss.org/browse/JBLOGGING-114
Project: JBoss Logging
Issue Type: Bug
Reporter: Steve Ebersole
Assignee: James Perkins
Apparently jboss-logging places a non-optional dependency on log4j:
{noformat}
[22:04] <sebersole> dmlloyd: if you are around...
[22:04] <sebersole> we are having trouble with hibernate-osgi because of
jboss-logging jar
[22:04] <sebersole> it essentially requires log4j
[22:05] <sebersole> [22:03] <brmeyer> their manifest has resolution:=optional
for every org.apache.log4j package *except* for .message
[22:05] <sebersole> tbh, thats all just gibberish to me. he might as well be
speaking chinese
[22:06] <sebersole> but when we try to deploy into karaf, we do get errors
installing our features because the jboss-logging bundle fails to start because log4j isnt
installed
[22:06] <sebersole> it works when we install log4j first as well
[22:06] <sebersole> even though we are not using log4j
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)