[
https://issues.apache.org/jira/browse/HADOOP-18620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684954#comment-17684954
]
ASF GitHub Bot commented on HADOOP-18620:
-----------------------------------------
virajjasani opened a new pull request, #5356:
URL: https://github.com/apache/hadoop/pull/5356
As discussed on the parent Jira HADOOP-15984, we do not have any
grizzly-http-servlet version available that uses Jersey 2 dependencies.
version 2.4.4 contains Jersey 1 artifacts:
https://repo1.maven.org/maven2/org/glassfish/grizzly/grizzly-http-servlet/2.4.4/grizzly-http-servlet-2.4.4.pom
The next higher version available is 3.0.0-M1 and it contains Jersey 3
artifacts:
https://repo1.maven.org/maven2/org/glassfish/grizzly/grizzly-http-servlet/3.0.0-M1/grizzly-http-servlet-3.0.0-M1.pom
Moreover, we do not use grizzly-http-* modules extensively. We use them only
for few tests such that we don't have to implement all the methods of
HttpServletResponse for our custom test classes.
We should get rid of grizzly-http-servlet, grizzly-http and
grizzly-http-server artifacts of org.glassfish.grizzly and rather implement
HttpServletResponse directly to avoid having to depend on grizzly upgrades as
part of overall Jersey upgrade.
> Avoid using grizzly-http-* APIs
> -------------------------------
>
> Key: HADOOP-18620
> URL: https://issues.apache.org/jira/browse/HADOOP-18620
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
>
> As discussed on the parent Jira HADOOP-15984, we do not have any
> grizzly-http-servlet version available that uses Jersey 2 dependencies.
> version 2.4.4 contains Jersey 1 artifacts:
> [https://repo1.maven.org/maven2/org/glassfish/grizzly/grizzly-http-servlet/2.4.4/grizzly-http-servlet-2.4.4.pom]
> The next higher version available is 3.0.0-M1 and it contains Jersey 3
> artifacts:
> [https://repo1.maven.org/maven2/org/glassfish/grizzly/grizzly-http-servlet/3.0.0-M1/grizzly-http-servlet-3.0.0-M1.pom]
>
> Moreover, we do not use grizzly-http-* modules extensively. We use them only
> for few tests such that we don't have to implement all the methods of
> HttpServletResponse for our custom test classes.
> We should get rid of grizzly-http-servlet, grizzly-http and
> grizzly-http-server artifacts of org.glassfish.grizzly and rather implement
> HttpServletResponse directly to avoid having to depend on grizzly upgrades as
> part of overall Jersey upgrade.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
