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

Steve Loughran commented on HADOOP-19694:
-----------------------------------------

When I do a thirdparty build I now get a warning of duplicate module 9 info.
{code}
[INFO] No artifact matching filter org.checkerframework:checker-qual
[WARNING] error_prone_annotations-2.36.0.jar, guava-33.4.8-jre.jar, 
failureaccess-1.0.3.jar, jspecify-1.0.0.jar, j2objc-annotations-3.0.0.jar 
define 1 overlapping classes: 
[WARNING]   - META-INF.versions.9.module-info
[WARNING] maven-shade-plugin has detected that some class files are
[WARNING] present in two or more JARs. When this happens, only one
[WARNING] single version of the class is copied to the uber jar.
[WARNING] Usually this is not harmful and you can skip these warnings,
[WARNING] otherwise try to manually exclude artifacts based on
[WARNING] mvn dependency:tree -Ddetail=true and the above output.
[WARNING] See http://maven.apache.org/plugins/maven-shade-plugin/
{code}
This is new.

given we want this to work on java17+ , we need to come up with a way of 
resolving the conflict, at the very least by making the guava one dominant.





> Bump guava to  33.4.8-jre due to EOL
> ------------------------------------
>
>                 Key: HADOOP-19694
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19694
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: hadoop-thirdparty
>            Reporter: Rohit Kumar
>            Assignee: Rohit Kumar
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> We can use the latest 33.4.8-jre version as the current one is quite old.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to