on
> typical classpath usage scenarios. If there's no way for you to run your
> application without the test classpath, then you can set the config file
> system property (log4j.configurationFile) to manually specify the path to
> the file.
>
> On 23 November 2017 at 02:08, Sverre Mo
Running my main application in Eclipse it is using the log4j2-test.xml
configuration, and not the log4j2.xml configuration.
src/main/resources/log4j2.xml
src/test/resources/log4j2-test.xml
I am not running a test application under src/test, but my main application
under src/main/
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 found out why. It
> > is for backward compatibility. And it is actually implied with your
&
> > <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=3cb22e02da6fba1475f01d8c17df28d2f89a570d;hb=HEAD>
> >
> > Ralph
> >
> >> On Jun 25, 2018, at 11:26 AM, Sverre Moe wrote:
> >
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:
. jun. 2018 kl. 21:21 skrev 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
Apache Log4j may have a wrong Automatic-Module-Name
requires org.apache.logging.log4j.core;
I cannot use the Logger and LogManager classes because they are not
accessible to my module.
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
private Logger logger =
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
>
it having to scan for a configuration file and
then choosing a test configuration.
/Sverre
2017-11-24 23:08 GMT+01:00 Sverre Moe <sverre@gmail.com>:
> I am running the application in Eclipse. Perhaps it adds the test classpath,
> even though I am not running a test applica
Using static initialization of two log4j properties on top of my main
application.
static {
System.setProperty("Log4jContextSelector",
"org.apache.logging.log4j.core.async.AsyncLoggerContextSelector");
System.setProperty("log4j.configurationFactory",
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
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 havin
12 matches
Mail list logo
