Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Ralph Goers
I can’t really answer that. I personally don’t use Eclipse or cradle. FWIW, we were advised by the Java module team to put module-info.java where it is for the reasons you stated. Ralph > On Jun 25, 2018, at 12:40 PM, Sverre Moe wrote: > > Disregard my final question. Did some research and

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Sverre Moe
Disregard my final question. Did some research and found out why. It is for backward compatibility. And it is actually implied with your latest sentence also, “earlier versions of Java will ignore it”. Is there a method to get this working with Eclipse and the gradle javadoc task? Den man. 25.

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Sverre Moe
Running Java 10 Eclipse cannot find the module. module no.djviking.movies { requires org.apache.logging.log4j; } Eclipse: org.apache.logging.log4j cannot be resolved to a module Running Eclipse 4.7.3 also on Java 10. However building with Gradle works having the module-info in that place.

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Ralph Goers
I should have said “earlier versions of Java will ignore it”. Ralph > On Jun 25, 2018, at 11:44 AM, Ralph Goers wrote: > > The module-info.java file is in classes/META-INF/versions/9. Java 9+ will > find it there. Other versions of Java will ignore it. > > If you want to look at the source

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Sverre Moe
The only module name that comes up in Eclipse is org.apache.logging.log4j.core, wirh both log4j-api and log4j-core on modulepath. compile group: 'org.apache.logging.log4j', name: 'log4j-api', version: '2.11.0' compile group: 'org.apache.logging.log4j', name: 'log4j-core', version:

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Ralph Goers
Log4j-API is not an automatic module. It has a module-info.java file. Log4j-API does not “require” log4j-core. It’s module-info specification is exports org.apache.logging.log4j; exports org.apache.logging.log4j.message; exports org.apache.logging.log4j.simple; exports

Re: Wrong Exports and Automatic Module Name

2018-06-25 Thread Matt Sicker
Can you add a JIRA report for this? On Sun, 24 Jun 2018 at 17:52, Sverre Moe wrote: > Perhaps the problem is that log4j-api.jar does not have a > Automatic-Module-Name in its MANIFEST.MF. > Only the log4j-core.jar has this entry in its manifest file. > Den lør. 23. jun. 2018 kl. 14:00 skrev

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

2018-06-25 Thread Remko Popma
(Re-posting since I did not see the link when sending from my yahoo mail account.) Blogged: https://blogs.apache.org/logging/entry/announce-apache-log4j-audit-1 Please share on social media! Thanks, -Remko On Mon, Jun 25, 2018 at 7:48 PM, Remko Popma wrote: > Blogged: [ANNOUNCE] Apache Log4j

Re: [ANNOUNCE] Apache Log4j Audit 1.0.0 released

2018-06-25 Thread Remko Popma
Blogged: [ANNOUNCE] Apache Log4j Audit 1.0.0 released : Apache Logging Services | | | | [ANNOUNCE] Apache Log4j Audit 1.0.0 released : Apache Logging Services | | | Please share on social media! Thanks,-Remko On Saturday, June 23, 2018, 1:31:26 AM GMT+9, Matt Sicker wrote:

A second configuration is loaded and overwrites mine

2018-06-25 Thread Alexander Magnusson
Hello! Setup: Embedded tomcat 8.5.31 Log4j2 api/core/web 2.11.0 Disruptor 3.3.6 >From my understanding by running in a web context scenario (my problem is in an embedded Tomcat 8.5.31) the log4j2.xml file needs only to be put into the web/WEB-INF/ folder for it to be read and the rest of the