You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "PJ Fanning (Jira)" <ji...@apache.org> on 2023/02/10 10:52:00 UTC
[jira] [Comment Edited] (HADOOP-18619) replace jsr311-api dependency with rs-api
[ https://issues.apache.org/jira/browse/HADOOP-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687023#comment-17687023 ]
PJ Fanning edited comment on HADOOP-18619 at 2/10/23 10:51 AM:
---------------------------------------------------------------
I haven't tried playing with jersey-core too much yet. I just know it doesn't compile if you switch out jsr311-api and use rs-api jar instead. It might be a few days before I can get back to it but if I can work out what if any code changes I need to make to my local copy of jersey-core, to get it to compile and test ok with rs-api jar - then I think I'll have a better idea of whether shading is an option or if we're stuck with forking the code and making some changes to the forked copy (which should be small enough, if needed).
was (Author: pj.fanning):
I haven't tried playing with jersey-core too much yet. I just know it doesn't compile if you switch out jsr311-api and use rs-api jar instead. It might be a few days before I can get back to it but if I can work out what if any code changes I need to make to my local copy of jersey-core to get it to compile and test ok with rs-api jar - then I think I'll have a better idea of whether shading is an option or if we're stuck with forking the code and making some changes to the forked copy (which should be small enough, if needed).
> replace jsr311-api dependency with rs-api
> -----------------------------------------
>
> Key: HADOOP-18619
> URL: https://issues.apache.org/jira/browse/HADOOP-18619
> Project: Hadoop Common
> Issue Type: Task
> Components: build, common
> Reporter: PJ Fanning
> Priority: Major
>
> [jsr311-api|https://mvnrepository.com/artifact/javax.ws.rs/jsr311-api] is unmaintained and causes issues when jars bring in a dependency on the newer [rs-api|https://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api/2.1.1] jar - that uses the same package name but has incompatible code
> To make things worse, there is now a jakarta fork of rs-api but I suggest we worry about that later.
> jersey-core 1.19.x gives us the jsr311-api dependency.
> The upgrade to HADOOP-15984 is currently blocked and looks hard.
> HADOOP-15983 is a workaround that allows us to keep jersey 1.x but removes the issue where we end up relying on the unmaintained Jackson 1.9 jars.
> We may now need a similar fork of jersey-core 1.19 to build a version of that jar that uses rs-api instead of jsr311.
> The main benefit here is get around the fact that jackson jaxrs 2.13+ has dropped support for jsr311 and now only supports rs-api. (see HADOOP-18332)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org