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

ASF GitHub Bot updated HADOOP-20013:
------------------------------------
    Labels: pull-request-available  (was: )

> HADOOP - Remove the duplicate javax.annotation-api from the classpath
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-20013
>                 URL: https://issues.apache.org/jira/browse/HADOOP-20013
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: build, common
>            Reporter: Jose Luis López
>            Priority: Major
>              Labels: pull-request-available
>
> *Scope*:
> * hadoop-project/pom.xml: on javax-websocket-server-impl, exclude 
> javax.annotation:javax.annotation-api, which arrives through 
> jetty-annotations. jakarta.annotation-api 1.3.5 already provides the same 
> javax.annotation classes.
> * LICENSE-binary and NOTICE-binary: replace 
> javax.annotation:javax.annotation-api:1.3.2 with 
> jakarta.annotation:jakarta.annotation-api:1.3.5. The jakarta jar is already 
> bundled (through jersey-common) but is missing from LICENSE-binary.
> *Why*: two jars publish the javax.annotation packages, and which one a module 
> sees depends on jar order.
> *Impact on Jetty 9*: none. Same classes.
> *Downstream*:
> * hadoop-yarn-server-nodemanager, the only module that declares 
> javax-websocket-server-impl: its consumers no longer get javax.annotation-api 
> 1.3.2. jakarta.annotation-api 1.3.5 provides the same javax.annotation 
> classes.
> * hadoop-client-minicluster: loses its relocated copy of javax.annotation-api 
> and keeps the relocated jakarta.annotation-api. Not API.
> * hadoop-client-api, hadoop-client-runtime: unchanged.
> *CI*: touches hadoop-project, so a full build.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to