Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.9.1
-
None
-
None
Description
To fully support Java 9 all Log4j jars must (at least) be packaged as automatic modules. We should, as much as possible, follow the recommendations at http://blog.joda.org/2017/05/java-se-9-jpms-automatic-modules.html. Given that the module names would be:
| Artifact ID | Module name |
|---|---|
| log4j-api | org.apache.logging.log4j |
| log4j-core | org.apache.logging.log4j.core |
| log4j-1.2-api | org.apache.log4j |
| log4j-appserver | org.apache.logging.log4j.appserver |
| log4j-flume-ng | org.apache.logging.log4j.flume |
| log4j-iostreams | org.apache.logging.log4j.iostreams |
| log4j-jcl | org.apache.logging.log4j.jcl |
| log4j-jmx-gui | org.apache.logging.log4j.jmx.gui |
| log4j-jul | org.apache.logging.log4j.jul |
| log4j-cassandra | org.apache.logging.log4j.cassandra |
| log4j-couchdb | org.apache.logging.log4j.couchdb |
| log4j-mongodb | org.apache.logging.log4j.mongodb |
| log4j-osgi | org.apache.logging.log4j.osgi |
| log4j-sl4j-impl | org.apache.logging.log4j.slf4j.impl* |
| log4j-to-slf4j | org.apache.logging.log4j.slf4j |
| log4j-taglib | org.apache.logging.log4j.taglib |
| log4j-web | org.apache.logging.log4j.web |
- log4j-liquibase uses a package name outside the org.apache.logging.log4j namespace so is not modularized.
- log4j-slf4j-impl cannot currently be modularized until the binding is modified. It cannot have classes in the org.slf4j namespace.
- log4j-slf4j-impl and log4j-to-slf4j both use the same package name - org.apache.logging.log4j.slf4j. This will remain the same as it will prevent them both from being loaded at the same time.
Attachments
Issue Links
- Dependent
-
LOG4J2-2076 Split up log4j-nosql into one module per appender
-
- Closed
-