[ https://issues.apache.org/jira/browse/TEZ-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393278#comment-17393278 ]
Takanobu Asanuma commented on TEZ-4323: --------------------------------------- Thanks for filing the issue, [~abstractdog]. I had created a similar jira for hadoop-3.3 by TEZ-4322. Strangely enough, building tez with hadoop-3.3.1 generates some jetty jars, though still not enough (there are not jetty-servlet, jetty-webapp, etc ) {noformat} $ tez git:(master) mvn clean package -Dhadoop.version=3.3.1 -DskipTests -Dmaven.javadoc.skip=true -Dallow.root.build=true ... $ tez git:(master) find tez-dist/target | grep jetty tez-dist/target/tez-0.10.2-SNAPSHOT/lib/jetty-io-9.4.40.v20210413.jar tez-dist/target/tez-0.10.2-SNAPSHOT/lib/jetty-util-9.4.40.v20210413.jar tez-dist/target/tez-0.10.2-SNAPSHOT/lib/jetty-http-9.4.40.v20210413.jar tez-dist/target/tez-0.10.2-SNAPSHOT/lib/jetty-client-9.4.40.v20210413.jar {noformat} > Jetty jars were removed from dist package with TEZ-4114 > -------------------------------------------------------- > > Key: TEZ-4323 > URL: https://issues.apache.org/jira/browse/TEZ-4323 > Project: Apache Tez > Issue Type: Bug > Affects Versions: 0.10.0, 0.10.1 > Reporter: László Bodor > Priority: Major > > Even after we agreed that we're about to ship jetty as part of the tez dist > package (see history in TEZ-4114 for details). This needs to be fixed: the > goal was to remove every possible jetty direct dependency from tez but still > let it ship hadoop's jetty as a transitive dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)