Skip to content
This repository was archived by the owner on Jan 9, 2020. It is now read-only.

Conversation

@mccheah
Copy link

@mccheah mccheah commented Aug 5, 2017

This probably is not the correct fix long-term as we should find the specific module that is pulling in the bad jersey-1 version. But until we can track down what the specific offending module is, this will have to do.

This probably is not the correct fix long-term as we should find the
specific module that is pulling in the bad jersey-1 version. But until
we can track down what the specific offending module is, this will have
to do.
@mccheah
Copy link
Author

mccheah commented Aug 5, 2017

cc @ifilonenko @erikerlandson

@erikerlandson
Copy link
Member

rerun integration tests please

@erikerlandson
Copy link
Member

erikerlandson commented Aug 5, 2017

4/4 successful so far

@erikerlandson
Copy link
Member

rerun integration tests please

3 similar comments
@erikerlandson
Copy link
Member

rerun integration tests please

@erikerlandson
Copy link
Member

rerun integration tests please

@ifilonenko
Copy link
Member

rerun integration tests please

@foxish
Copy link
Member

foxish commented Aug 7, 2017

Looks like the right fix to me. (for the short term)

@erikerlandson
Copy link
Member

This fix (#420) passed all integration-testing runs (except one that failed for some unrelated reason). I'm still curious why #419 passed 5/6 times without addressing the jar conflict at all.

Regardless, LGTM

@foxish
Copy link
Member

foxish commented Aug 7, 2017

Thoughts on whether we should use this fix or the one in #419 ?

@erikerlandson
Copy link
Member

I think we should merge #420. Merging #419 might also be useful; it reduced failures by ~80%, which makes it a potentially good defensive change against CI failures from lengthy startup times.

@erikerlandson erikerlandson merged commit 5fdaa7f into branch-2.2-kubernetes Aug 8, 2017
@ash211 ash211 deleted the exclude-jersey-docker-minimal-bundle branch August 9, 2017 17:10
ifilonenko pushed a commit to ifilonenko/spark that referenced this pull request Feb 26, 2019
…9.1-palantir.10

Sr/hadoop 2.9.1 palantir.11
puneetloya pushed a commit to puneetloya/spark that referenced this pull request Mar 11, 2019
…8s#420)

This probably is not the correct fix long-term as we should find the
specific module that is pulling in the bad jersey-1 version. But until
we can track down what the specific offending module is, this will have
to do.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants