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

Jose Luis López updated HADOOP-20013:
-------------------------------------
    Summary: HADOOP - Remove the duplicate javax.annotation-api and declare 
jetty-http in the shuffle  (was: HADOOP — Remove the duplicate 
javax.servlet-api and javax.annotation-api from the classpath)

> HADOOP - Remove the duplicate javax.annotation-api and declare jetty-http in 
> the shuffle
> ----------------------------------------------------------------------------------------
>
>                 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
>
> *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.
> * hadoop-mapreduce-client-shuffle/pom.xml: ShuffleChannelHandler imports 
> org.eclipse.jetty.http.HttpHeader. Declare org.eclipse.jetty:jetty-http.
> * hadoop-project/pom.xml: manage jetty-http at ${jetty.version}. It is not 
> managed today.
> * LICENSE-binary: drop javax.annotation:javax.annotation-api, if listed.
> *Why*: two jars publish the javax.annotation packages, and which one a module 
> sees depends on jar order. The shuffle compiles against jetty-http that it 
> gets only transitively.
> *Impact on Jetty 9*: none. Same classes; jetty-http already resolves at 
> 9.4.58.
> *Downstream*: none for the shaded clients. Direct consumers no longer get 
> javax.annotation-api; jakarta.annotation-api provides the same classes.
> *CI*: touches hadoop-project, so a full build.



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