[
https://issues.apache.org/jira/browse/LOG4J2-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005509#comment-17005509
]
Matt Sicker commented on LOG4J2-2649:
-------------------------------------
I mostly live in the Jenkins world for Java, and we haven’t done any GraalVM
work yet (we were focused on Java 11 support last year). I’ve been
experimenting with a new plugin system which might theoretically be able to
avoid reflection entirely by using generated metadata classes at annotation
processing time (like Micronaut for example), though that’s for 3.x. In 2.x, a
patch to use the old reflection API or a wrapper like we do for StackWalker
would be some possible approaches.
> Is Log4j2 considered to support successful static compilation under GraalVM?
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-2649
> URL: https://issues.apache.org/jira/browse/LOG4J2-2649
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: YangGuanchao
> Priority: Blocker
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Oracle released GraalVM [https://github.com/oracle/graal] to support the
> static compilation of Java applications to Native Image, which can increase
> the startup speed of Java by at least 10 times. In the cloud native field,
> this basic technology is believed to be in the near future. Will be supported
> by more and more vendors, such as the Spring/Spring Boot community has
> supported or plans to support the feature of GraalVM, see this issue:
> [https://github.com/spring-projects/spring-framework/search?q=Graalvm&type=Issues]
> can support static compilation, so it is recommended that Log4j2 also need
> to support static compilation as soon as possible, and can be compiled
> correctly under GraalVM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
