-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
None
Apparently jboss-logging places a non-optional dependency on log4j:
[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
- duplicates
-
JBLOGGING-113 OSGi header declares non-optional dependency to Log4j packages
- Resolved
- is related to
-
JBEE-160 jboss-transaction-api OSGi bundle requiring optional packages
- Resolved