test: option to run integration tests with modified dependencies #2561
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request explores the idea of running the integration
tests with modified dependency versions.
First, the integraiton test script (build.sh) compiles the project
with normal dependencies (the latest shared dependencies BOM).
After that, when it runs "mvn verify", it uses slightly modified
dependencies (
-Dgrpc.version=1.72.0
in this case), withoutre-compiling the main source code by
-Dmaven.main.skip
argument.This runtime is similar to what our library users would have when
they upgrade the 3rd-party dependencies in their builds, because
they do not recompile GCP client libraries.