There is a balance that needs to be struck here. We don’t want to add support
for OSGi at the cost of forcing non-OSGi users to have to include a bunch of
Log4j dependencies. That said, I suggest the other day that we might want to
split some things that a majority of our users will rarely use
Hey all,
Apachecon has been ended so I am following the promise I did - I’ve taken a
look on the log4j build to check what’s going on with OSGi stuff. Currently
OSGi bundles are split from main log4j-core which I think leads to maintanance
trouble also number of dependencies of log4j-core seems
https://issues.apache.org/bugzilla/show_bug.cgi?id=56389
Bug ID: 56389
Summary: Documentation for default initialization procedure is
incorrect
Product: Log4j
Version: unspecified
Hardware: All
OS: All
[
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966314#comment-13966314
]
Arne Molch edited comment on LOG4J2-435 at 4/11/14 7:52 AM:
Hi
[
https://issues.apache.org/jira/browse/LOG4J2-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966314#comment-13966314
]
Arne Molch commented on LOG4J2-435:
---
Hi, when will this issue be resolved? Tis is the ma
