[
https://issues.apache.org/jira/browse/HIVE-28885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941652#comment-17941652
]
Stamatis Zampetakis commented on HIVE-28885:
--------------------------------------------
The main reason that led me into creating this ticket are compilation failures
that appeared during the calcite upgrade to 1.33.0 (HIVE-27102).
The presence of the log4j annotation processor in conjunction with the
immutable annotations that are present in calcite leads to issues. As
investigated under LOG4J2-3609, the problem is not specific to log4j processor
but to annotation processors in general. All in all, it's better to disable
unnecessary annotation processors when they are not used to avoid this and
other similar issues.
> Disable unnecessary annotation processing
> -----------------------------------------
>
> Key: HIVE-28885
> URL: https://issues.apache.org/jira/browse/HIVE-28885
> Project: Hive
> Issue Type: Task
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
>
> Currently we don't make any use of annotation processors in the project.
> However, the log4j-core dependency contains an annotation processor and this
> has impact on the build. The following WARNING appears every time we build or
> test a module in the project and indicates that due to annotation processing
> compile avoidance is deactivated.
> {noformat}
> [WARNING] The following annotation processors were found on the classpath:
> [org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor],
> provided by
> /home/zabetak/.m2/repository/org/apache/logging/log4j/log4j-core/2.24.3/log4j-core-2.24.3.jar
> Compile avoidance has been deactivated.
> Please use the maven-compiler-plugin version 3.5 or above and use the
> <annotationProcessorPaths> configuration element to declare the processors
> instead.
> If you did not intend to use the processors above (e.g. they were leaked by a
> dependency), you can use the <proc>none</proc> option to disable annotation
> processing.
> For more information see
> https://gradle.com/help/maven-extension-compile-avoidance.
> {noformat}
> Apart from compile avoidance the use of annotation processing can have other
> side effects during the build and it can even lead to cryptic compilation
> failures.
> I propose to disable annotation processing explicitly to avoid the warnings
> above, exploit compile avoidance, and avoid cryptic compilation errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
