-
Notifications
You must be signed in to change notification settings - Fork 96
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
[WIP] ISSUE-1340 Upgrade jackson and relevant dependencies (directly and indirectly) #1341
base: master
Are you sure you want to change the base?
Conversation
Since it touches various dependencies we may not feel safe to just rely on unit test. We may need to step back and not rush it... Which tests should we perform before merge this? If we feel safe to rely on system tests we need to merge so we have contradiction here. |
pom.xml
Outdated
<!-- Ideally we need to use official version of SR: wait for new release --> | ||
<schema-registry.version>0.6.0.3.4.0.0-145</schema-registry.version> | ||
<!-- This version should be changed to actual HDF-3.4.0.0-146 version when it is published --> | ||
<schema-registry.version>0.6.1-SNAPSHOT-HDF-3.4.0.0-146-maybe</schema-registry.version> |
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.
Should be changed to 3.4.0.0-146 (or higher) or new official SR version.
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.
Agree to keep the HDF version until the new SR version is pushed.
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.
The changes looks good. For testing we need to rely on system tests. Maybe you can point your branch to canary and trigger a build + test (assuming that the streamline system tests run as a part of canary)
pom.xml
Outdated
<curator.version>2.11.0</curator.version> | ||
<dropwizard.version>1.0.5</dropwizard.version> | ||
<curator.version>4.0.1</curator.version> | ||
<curator.test.version>2.12.0</curator.test.version> |
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.
is it ok to have different version just for test ?
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.
I picked it up from Registry project, but it doesn't look like needed for Streamline. Will remove.
…directly) This patch brings change of huge dependencies so should be tested thoughtfully. Change-Id: Ic02c92aeb302a79b68598f6e0e66f18165fd2b43
Change-Id: I924e9508aa70c0340785d2da9234d1769e7a7eb3
Change-Id: Ib16f1c70872ae6eed54649cefca5235f9fe2ce60
This patch brings change of huge dependencies so should be tested thoughtfully.
The build passed with custom build of SR, and I'll upgrade once the version is available in HWX repo. After that we can check whether the build passes in Travis CI.
This closes #1340