This repository has been archived by the owner on Apr 23, 2019. It is now read-only.
Make complete distribution depend on components #33
Conversation
This file contains 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
Rather than creating an uber-jar, this changes the cava.jar to only be a pom-only source of dependency information for including all the jars for each cava component. The uber-javadoc jar is still published. Doing so resolves a potential dependency conflict situation, where a library depends on a single cava component, and a project includes both that library and the cava uber-jar. The PR also adjusts dependencies to ensure necessary libraries are automatically included when using a single cava component. Larger dependencies are excluded from the dependency tree when using the complete cava distrubtion and must still be added explicitly.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Rather than creating an uber-jar, this changes the cava.jar to only be a pom-only source of dependency information for including all the jars for each cava component. The uber-javadoc jar is still published.
Doing so resolves a potential dependency conflict situation, where a library depends on a single cava component, and a project includes both that library and the cava uber-jar.
The PR also adjusts dependencies to ensure necessary libraries are automatically included when using a single cava component. Larger dependencies are excluded from the dependency tree when using the complete cava distrubtion and must still be added explicitly.