-
Notifications
You must be signed in to change notification settings - Fork 9k
YARN-11498. Exclude jettison from jersey-json artifact as on older version is being pulled #5623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…version is being pulled
@szilard-nemeth Could you please see this is it is okay? |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Hi @devaspatikrishnatri , you can re-trigger the build by creating an empty commit I think the reason for this exclusion should be documented in the Jira, as far as I know the reason being:
https://mvnrepository.com/artifact/com.sun.jersey/jersey-json/1.19.4 BTW jackson-mapper-asl 1.9.2 has also 2 CVEs (https://mvnrepository.com/artifact/org.codehaus.jackson/jackson-mapper-asl/1.9.2). |
💔 -1 overall
This message was automatically generated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@devaspatikrishnatri thanks, LGTM.
The other exclude can be done in a separate ticket and pull request.
The latest yetus run was OK, the test4tests is not relevant here.
Thanks @devaspatikrishnatri for the patch, @tomicooler for the review. Merging to trunk. |
@ayushtkn @steveloughran it would probably make sense to backport this to the v3.3 branch |
ok: can someone do a backport PR for a test run? |
I ran https://issues.apache.org/jira/browse/YARN-11498 provides no evidence of the problem it is trying to fix. Is this PR even needed? |
maven picks up closest version to the root; ivy (hence gradle and SBT) does it differently. Sometimes downstream projects break even though hadoop is happy. this makes it worthwhile |
Thanks for the feedback Steve. This PR adds the exclusion to just one place where jersey-json is imported. Should it not add the exclusion in all places where jersey-json is imported? I can create a follow to this PR for trunk that does that. And then create a backport PR that includes this PR and my new PR. |
I tried a cherrypick to branch-3.3 and the build failed as there's no explicit jettison import in that branch
|
…version is being pulled
Description of PR
How was this patch tested?
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?