Repository navigation
Migrate usage of internal GSON API - #324
Conversation
…rrors for GSON 2.14.0 upgrade
|
Hi @renner, we currently struggle with using this project in our now-to-be spring boot 4 application. Is there still anything we need to do from our side in order for the GSON library to be upgrade here? |
|
@rjmateus if in doubt, I can remove the GSON version upgrade in this PR and only keep the migration of internal GSON calls. The salt API then works with GSON |
|
@SoulKa I think it would be better (and allow us to move faster) if the gson upgrade is done in a separate PR. |
|
@rjmateus thank you for your fast response in this matter. I reverted the GSON version upgrade and the tests still run locally. |
There was a problem hiding this comment.
LGTM.
The version bump is a kind of a blocker for us at the moment, since the version we use needs to remain in sync with what openSUSE provides. This change however works without any issue on 2.8.9 as well, and actually improves the existing code. Thanks for your contribution!
|
The SaltClientDockerTest fails since |
Apologies, by mistake I deleted mbologna/docker-salt. Now I revived and renovated it, and pushed the missing images to Docker Hub. All in all: you should relaunch the tests, the container pull will now work. should now be |
|
Thank you very much @mbologna! I launched the containers locally and ran all tests. The |
|
@mackdk are we ready to merge? |
|
@rjmateus anything left that blocks this PR? :) |
Closes #323
com.google.gson.internalpackages to support the usage of newer GSON versions