[ 
https://issues.apache.org/jira/browse/HIVE-29347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041230#comment-18041230
 ] 

Raghav Aggarwal commented on HIVE-29347:
----------------------------------------

Yes, you are right, was running build locally with the following profiles and 
didn't encounter the issue. But as CI don't use errorProne profile, it failed.
{code:java}
mvn clean install -DskipTests -PerrorProne,itests,dist,qsplits -Drat.skip=true 
-Dmaven.javadoc.skip {code}
Will update the scope of PR to consider only surefire and spotless. As surefire 
is moved from 2.22.0 -> 3.5.3 in HIVE-29336

it just a precautionary change for future in case we update pom version from 35 
to any future release.

> 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)

Reply via email to