Re: Wrong Exports and Automatic Module Name

Den fre. 10. aug. 2018 kl. 04:40 skrev Ralph Goers < ralph.go...@dslextreme.com>: > Is this related to > https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8208269? < > https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8208269?> > > Ralph > > Thanks for letting me know. I hope it will

Re: Wrong Exports and Automatic Module Name

Is this related to https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8208269? Ralph > On Aug 9, 2018, at 2:08 PM, Sverre Moe wrote: > > still no solution > > I have even tried with latest snapshots of JDK 11 and JDK 1

Re: Wrong Exports and Automatic Module Name

still no solution I have even tried with latest snapshots of JDK 11 and JDK 12, same problem. Den tor. 28. jun. 2018 kl. 00:07 skrev Sverre Moe : > Are there any known problems with the javadoc tool and log4j automatic > module? > > Running javadoc when having a requires org.apache.logging.log4j

Re: Wrong Exports and Automatic Module Name

Are there any known problems with the javadoc tool and log4j automatic module? Running javadoc when having a requires org.apache.logging.log4j fail as it cannot find the module. I have done the same as I do for compile, adding all jars on classpath to the modulepath, then clearing the classpath.

Re: Wrong Exports and Automatic Module Name

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 fo

Re: Wrong Exports and Automatic Module Name

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. ju

Re: Wrong Exports and Automatic Module Name

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. I

Re: Wrong Exports and Automatic Module Name

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 lo

Re: Wrong Exports and Automatic Module Name

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 look in https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=blob;f=log4j-api-java9/src/main/java/module-info.java;h=3cb22e0

Re: Wrong Exports and Automatic Module Name

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: '2.11.0'

Re: Wrong Exports and Automatic Module Name

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 org.apache.logging.log4j.sp

Re: Wrong Exports and Automatic Module Name

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 Sver

Re: Wrong Exports and Automatic Module Name

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 Sverre Moe : > > Apache Log4j may have a wrong Automatic-Module-Name > requires org.apache.logging.