[ https://issues.apache.org/jira/browse/LOG4J2-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-34. ----------------------------- Resolution: Incomplete Closing this issue since it is overlaps the OSGi issues and doesn't really propose anything tangible. > log4j 2 should be modular > ------------------------- > > Key: LOG4J2-34 > URL: https://issues.apache.org/jira/browse/LOG4J2-34 > Project: Log4j 2 > Issue Type: Wish > Reporter: Curt Arnold > > See > http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201004.mbox/%3c5230a295-dddd-42d1-934a-3577b5997...@gmail.com%3e > and following. > log4j 1.2's contained substantial tangental code such as obsolete versions of > LogFactor5 and Chainsaw. > Log4j 2 should be much more modular, possibly involving use of OSGi (see > https://issues.apache.org/jira/browse/LOG4J2-10) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org