[ 
https://issues.apache.org/jira/browse/HDDS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei-Chiu Chuang updated HDDS-3377:
----------------------------------
    Description: 
I missed this during HDDS-3000

guava-26.0-android is not used but if it's in the classpath (copied explicitly 
in pom file), it could potentially load this one and cause runtime error.

{noformat}
$ find . -name guava*
./hadoop-ozone/ozonefs-lib-legacy/target/classes/libs/META-INF/maven/com.google.guava/guava
./hadoop-ozone/dist/target/ozone-0.4.0.7.1.1.0-SNAPSHOT/share/ozone/lib/guava-26.0-android.jar
./hadoop-ozone/dist/target/ozone-0.4.0.7.1.1.0-SNAPSHOT/share/ozone/lib/guava-28.2-jre.jar
{noformat}

  was:
I missed this during HDDS-3000

guava-26.0-android is not used but if it's in the classpath (copied explicitly 
in pom file), it could potentially load this one and cause runtime error.


> Remove guava 26.0-android jar
> -----------------------------
>
>                 Key: HDDS-3377
>                 URL: https://issues.apache.org/jira/browse/HDDS-3377
>             Project: Hadoop Distributed Data Store
>          Issue Type: Task
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I missed this during HDDS-3000
> guava-26.0-android is not used but if it's in the classpath (copied 
> explicitly in pom file), it could potentially load this one and cause runtime 
> error.
> {noformat}
> $ find . -name guava*
> ./hadoop-ozone/ozonefs-lib-legacy/target/classes/libs/META-INF/maven/com.google.guava/guava
> ./hadoop-ozone/dist/target/ozone-0.4.0.7.1.1.0-SNAPSHOT/share/ozone/lib/guava-26.0-android.jar
> ./hadoop-ozone/dist/target/ozone-0.4.0.7.1.1.0-SNAPSHOT/share/ozone/lib/guava-28.2-jre.jar
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to