fix: servicetalk-data-jackson dependency scopes #2198
Merged
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.
Motivation:
The
servicetalk-data-jackson-jersey
module exposes types that arelocated in the
servicetalk-data-jackson
module. Similarly, theservicetalk-data-jackson
module exposes types that are in theservicetalk-serializer-api
andservicetalk-serialization-api
modules.Dependencies that contain types exposed in a module's API should be imported using
api
scope but currently these dependencies are imported using onlyimplementation
scope. Attempting to use the types results in aClassNotFoundException
.Modifications:
servicetalk-data-jackson
to anapi
dependency ofservicetalk-data-jackson-jersey
servicetalk-serializer-api
andservicetalk-serialization-api
toapi
dependencies ofservicetalk-data-jackson
Result:
Consumers of the
servicetalk-data-jackson-jersey
andservicetalk-data-jackson
modules will be able to reference all types exposed in these modules' APIs without class not found errors or the need to explicitly importservicetalk-data-jackson
,servicetalk-serializer-api
orservicetalk-serialization-api
modules.