[ 
https://issues.apache.org/jira/browse/HADOOP-18332?focusedWorklogId=790131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-790131
 ]

ASF GitHub Bot logged work on HADOOP-18332:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Jul/22 19:22
            Start Date: 12/Jul/22 19:22
    Worklog Time Spent: 10m 
      Work Description: pjfanning commented on PR #4547:
URL: https://github.com/apache/hadoop/pull/4547#issuecomment-1182339223

   @ayushtkn I had those changes ready to commit before I closed this PR - I've 
merged them now - we'll see how this build goes




Issue Time Tracking
-------------------

    Worklog Id:     (was: 790131)
    Time Spent: 1h 50m  (was: 1h 40m)

> remove rs-api dependency (needs jackson downgrade to 2.12.7)
> ------------------------------------------------------------
>
>                 Key: HADOOP-18332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18332
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>            Reporter: PJ Fanning
>            Assignee: PJ Fanning
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> This jsr311-api jar seems to conflict with newly added rs-api jar dependency 
> - they have many of the same classes (but conflicting copies) - jersey-core 
> 1.19 needs jsr311-api to work properly (and fails if rs-api used instead)
> * https://mvnrepository.com/artifact/javax.ws.rs/jsr311-api
> * https://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api
> Seems we will need to downgrade jackson to 2.12.7 because of jax-rs 
> compatibility issues in jackson 2.13 (see 
> https://github.com/FasterXML/jackson-jaxrs-providers/issues/134)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to