[
https://issues.apache.org/jira/browse/HIVE-29347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041229#comment-18041229
]
Stamatis Zampetakis commented on HIVE-29347:
--------------------------------------------
[~Aggarwal_Raghav] Leaving the decision up to you. Personally, I try to tackle
one problem at a time. For instance, surefire changes were always causing some
additional headache so its usually better to have them isolated from others and
as you can see in HIVE-28885 the same goes for log4j stuff. Some changes appear
very innocent and trivial at first but then they uncover other hurdles.
> Fix maven plugin related warning during build
> ---------------------------------------------
>
> Key: HIVE-29347
> URL: https://issues.apache.org/jira/browse/HIVE-29347
> Project: Hive
> Issue Type: Improvement
> Reporter: Raghav Aggarwal
> Assignee: Raghav Aggarwal
> Priority: Major
> Labels: pull-request-available
>
> Scope of this Jira is to fix:
> # spotless plugin warning for argLine
> # Use correct surefire version variable in
> standalone-metastore/metastore-rest-catalog/pom.xml
> # Use annotationProcessor for Log4j2
> standalone-metastore/metastore-rest-catalog/pom.xml uses surefire.version but
> instead it should be maven.surefire.plugin.version. as it was running with
> maven surefire 2.22.0 version before HIVE-29336. Better to keep it consistent.
> {code:java}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>${surefire.version}</version>
> </plugin> {code}
> also Fix, in iceberg module during build
> {code:java}
> [WARNING] Parameter 'argLine' is unknown for plugin
> 'spotless-maven-plugin:2.44.4:check (validate)'{code}
> {code:java}
> [WARNING] The following annotation processors were found on the classpath:
> [org.apache.logging.log4j.core.config.plugins.processor.PluginProcessor],
> provided by
> /Users/raghav/.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. {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
