Unnecessary-looking dependencies
See original GitHub issueNew in Release 22 are a bunch of Maven dependencies that look like they should be compile-only, but are now required at runtime.
[INFO] +- com.google.guava:guava:jar:22.0:compile
[INFO] | +- com.google.code.findbugs:jsr305:jar:1.3.9:compile
[INFO] | +- com.google.errorprone:error_prone_annotations:jar:2.0.18:compile
[INFO] | +- com.google.j2objc:j2objc-annotations:jar:1.1:compile
[INFO] | \- org.codehaus.mojo:animal-sniffer-annotations:jar:1.14:compile
Issue Analytics
- State:
- Created 6 years ago
- Reactions:8
- Comments:28 (11 by maintainers)
Top Results From Across the Web
Is there a simple way to remove unused dependencies from a ...
DepClean is a tool to automatically remove dependencies that are included in your Java dependency tree but are not actually used in the...
Read more >Find Unused Maven Dependencies - Baeldung
In this short tutorial, we learned how to find unused maven dependencies. It's a good practice to check for unused dependencies regularly since ......
Read more >Refactoring to Improve Testability: Removing Unnecessary ...
This post explains how to refactor code to remove unnecessary dependencies, which is easily found when writing tests. Unnecessary dependencies ...
Read more >Maven – Optional Dependencies and Dependency Exclusions
Since Maven resolves dependencies transitively, it is possible for unwanted dependencies to be included in your project's classpath.
Read more >Package issue - Unnecessary dependencies and wrong name?
I expect the dependency 'Files' only but I'm also getting ... so if Xcode doesn't already give you the sort of scheme you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cpovirk’s conclusion above seems to have been that of the two options we have, both of which cause issues for some people in some way, we should stick with what we’re currently doing. So 23.0 will continue to have those dependencies as non-optional.
This is madness Just make them
provided
. Its how they should be declared If this declaration causes bugs then these bugs are somewhere else