-
Notifications
You must be signed in to change notification settings - Fork 30
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
[BUG] Depclean falsely reports a direct dependency as "UNUSED DIRECT DEPENDENCY" #108
Comments
Out of these 4, only
|
Hi @algomaster99, thanks for reaching out. The DepClean analysis results are ALL correct! Let me explain each case separately: Case
|
@cesarsotovalero Thanks for the prompt and elaborate reply!
This case is very clear to me. And thanks for pointing out that it could be replaced with the other transitive dependencies. It is always best to have the dependencies as direct if they are used in the program.
This is clear too. Thanks!
I think I got this confused with |
Describe the bug
Upon running
Depclean v2.0.1
on ASSERT-KTH/sorald@8762596, it reports four unused direct dependencies - out of whichorg.sonarsource.java:java-checks-testkit:6.9.0.23563
is definitely used here.To Reproduce
Steps to reproduce the behavior:
depclean-maven-plugin v2.0.1
without ignoring any scopes.Expected behavior
Report should not include
org.sonarsource.java:java-checks-testkit:6.9.0.23563:compile
.The text was updated successfully, but these errors were encountered: