[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000837#comment-16000837
]
Mikael Ståldal commented on LOG4J2-1359:
----------------------------------------
I don't use an IDE to build the project for the purpose of producing artifacts,
I don't think that's an important use case to be supported.
However, I do always use an IDE (IntelliJ IDEA) for development, and for that
purpose it is important that the IDE is able to compile the project, and also
run unit tests. I think that's an important use case.
After addition of the Java 9 stuff, I had to make some manual tweaks to the the
project in IntelliJ IDEA, and I still haven't got it to work perfectly
(although good enough to be usable).
See this thread in mailing list:
https://lists.apache.org/[email protected]:lte=6M:%22Java%209%20support%20has%22
> Add support for Java 9 StackWalker API in ReflectionUtil
> --------------------------------------------------------
>
> Key: LOG4J2-1359
> URL: https://issues.apache.org/jira/browse/LOG4J2-1359
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Environment: Java 1.9+
> Reporter: Matt Sicker
> Assignee: Ralph Goers
> Labels: jdk9
>
> [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html]
> Based on the functional nature of this API, supporting it may require
> compiling at least one class using javac 1.9 and reflectively loading it in
> ReflectionUtil similar to how Spring supports newer JDK APIs.
> Without support for StackWalker, ReflectionUtil will fall back to using a
> slower API in Java 1.9. This is because the Reflection class is a
> sun-internal class which are no longer exported to non-JDK code without
> setting special command line flags.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
