Martin Schröder created LOG4J2-2516:
---------------------------------------
Summary: log4j2 incompatible with Gradle 5.0
Key: LOG4J2-2516
URL: https://issues.apache.org/jira/browse/LOG4J2-2516
Project: Log4j 2
Issue Type: Bug
Affects Versions: 2.11.1
Reporter: Martin Schröder
Log4j2 can not be used with the recently released Gradle 5.0 because
{quote}Deprecated Gradle features were used in this build, making it
incompatible with Gradle 5.0.
{quote}
{quote}Putting annotation processors on the compile classpath has been
deprecated and is scheduled to be removed in Gradle 5.0. Please add them to the
processor path instead. If these processors were unintentionally leaked on the
compile classpath, use the -proc:none compiler option to ignore them..
{quote}
And yes, support for annotation processors has been removed in 5.0.
Discussions of these problems are
[here|https://discuss.gradle.org/t/regarding-the-annotation-processors-on-compile-classpath-warning-in-gradle-4-6/26144/2]
and [here|https://github.com/gradle/gradle/issues/5056]; please refer to them
for more information. I'm _not_ an expert on this issue, merely a user of both
Log4J2 and Gradle.
While Gradle has issued these warnings since at least 4.6, I did not find a
discussion about this in the log4j2 bug tracker (and the issue has not been
fixed yet).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
