[
https://issues.apache.org/jira/browse/LOG4J2-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005394#comment-17005394
]
Ralph Goers commented on LOG4J2-2649:
-------------------------------------
The problem you are running into is that AFAIK none of the Log4j committers
uses GraalVM. Since we do this in our spare time we primarily work on issues
that are interest to us which generally seems to be motivated by what we are
working on in our $day$ jobs. That leaves you with a few choices:
# Diagnose the issues, fix them, and then provide one or more pull requests.
# Hope that one of us has the time and interest to look into this.
# Consider sponsoring one of us to encourage us to be a bit more motivated.
> 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)
