[
https://issues.apache.org/jira/browse/LOG4J2-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789421#comment-17789421
]
Piotr Karwasz commented on LOG4J2-2438:
---------------------------------------
This should work with the current {{3.0.0-SNAPSHOT}} version.
I am not marking it as resolved, since we currently don't systematically test
it, but
[log4j-samples-jlink|https://github.com/apache/logging-log4j-samples/tree/main/log4j-samples-jlink]
can be tested against {{3.0.0-SNAPSHOT}} with the following invocation:
{noformat}
./mvnw verify -Dlog4j2.version=3.0.0-SNAPSHOT -pl log4j-samples-jlink
log4j-samples-jlink/target/maven-jlink/default/bin/java \
-m
org.apache.logging.log4j.samples.jlink/org.apache.logging.log4j.samples.jlink.Main
{noformat}
> Using log4j-core as a module and usage in JLink
> -----------------------------------------------
>
> Key: LOG4J2-2438
> URL: https://issues.apache.org/jira/browse/LOG4J2-2438
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.11.1
> Reporter: Karl Heinz Marbaise
> Priority: Critical
> Fix For: 3.0.0
>
>
> Currently based on the given automatic modules you can't use log4j-core in a
> project where you like to use jlink to produce a runtime image..
> Related to LOG4J2-2226
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
