[
https://issues.apache.org/jira/browse/HIVE-28885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis resolved HIVE-28885.
----------------------------------------
Fix Version/s: 4.3.0
Resolution: Fixed
Fixed in
https://github.com/apache/hive/commit/ca105f8124072d19d88a83b2ced613d326c9a26b
> 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
> Fix For: 4.3.0
>
>
> 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)
