[
https://issues.apache.org/jira/browse/HADOOP-15984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17915816#comment-17915816
]
PJ Fanning commented on HADOOP-15984:
-------------------------------------
Just my opinion but I think changing to jersey version 2 in a patch release is
not a good idea from a semver perspective. Is there any reason not to work to
releasing a v3.5.0 or a milestone release for 3.5 instead of doing a new 3.4.x
release?
[~bpatel] Jackson can probably be updated but I've already tried a few PRs and
typically run into issues - getting rid of Jersey v1 should make it easier to
upgrade but there may be other issues.
Examples:
* [https://github.com/apache/hadoop/pull/7022]
* [https://github.com/apache/hadoop/pull/6761]
> Update jersey from 1.19 to 2.x
> ------------------------------
>
> Key: HADOOP-15984
> URL: https://issues.apache.org/jira/browse/HADOOP-15984
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Akira Ajisaka
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> jersey-json 1.19 depends on Jackson 1.9.2. Let's upgrade.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
