joseluisll commented on PR #8893: URL: https://github.com/apache/hadoop/pull/8893#issuecomment-6626646643
Thanks @pan3793. The intent was to make the direct Jetty usage of each module visible in its own pom while we go from Jetty 9 to Jetty 12 ee8, and later to the jakarta namespace (ee10/ee11, HADOOP-19395). At that step `hadoop-common` may stop exporting some of these artifacts, and the modules that need them would then already declare them. Today it changes nothing: the dependency comparison shows the same resolution, since `hadoop-common` provides them at the same scope. I tend to prefer declaring direct dependencies for core pieces like Jetty, but that's a wider question, not this PR. If you'd still rather rely on transitive resolution here, I'll drop the pom changes and keep the Java changes, which are what Jetty 12 needs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
