Skip to content

Declare api and implementation dependencies to align with code usages #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 17, 2020

Conversation

labkey-susanh
Copy link
Contributor

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 api dependencies will assure that our published pom files are accurate and others will not have to separately declare some dependencies that we rely on when using our jar files.

The changes made here were done with the help of this Gradle dependency-analysis plugin, which is still not at v1.0 and seems to have a few quirks, but my spot checks of the suggestions given seem like they provide solid advice.

Changes

  • Update to latest Gradle version
  • Update dependency declarations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants