Don't declare jsii-runtime as a dependency of any component directly #2228
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.
Description of changes:
Don't declare jsii-runtime as a dependency of any component directly
this direct dependency that was added to some modules is a transitive
dependency of the cdk packages that are used just for testing.
The original intent of adding jsii-runtime as a dependency was to just
exclude the jackson version that are dependencies of it.
The scope of the dependency was missing when it should be
test which cause the dependency to be included in the
final jar of the connectors.
Instead I declare it in the top-level dependency management with its
exclusions so the dependency scope is unchanged
The test scope tag was also missing on a cdk dependency of the cloudwatch connector