Declare api and implementation dependencies to align with code usages#46
Merged
Conversation
labkey-jeckels
approved these changes
Sep 17, 2020
labkey-tchad
approved these changes
Sep 21, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Rationale
It is generally best practice to explicitly declare dependencies that are used in your code rather than relying on them to come through transitively. Though in reality the risk of these transitive dependencies disappearing is low and would be easily noticed, the declaration of proper dependencies will assure that our published
pomfiles are accurate and others will not have to separately declare some dependencies that we rely on when using our jar files.Related Pull Requests
Changes
jars.txt