-
Notifications
You must be signed in to change notification settings - Fork 45
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
[MDEP-708] - dependency:analyze recommends test scope for test-only artifacts that have non-test scope #14
Conversation
src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysis.java
Show resolved
Hide resolved
src/main/java/org/apache/maven/shared/dependency/analyzer/ProjectDependencyAnalysis.java
Outdated
Show resolved
Hide resolved
...t/java/org/apache/maven/shared/dependency/analyzer/DefaultProjectDependencyAnalyzerTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is having trouble:
Only fails on a couple of nodes, but it does look related
Thought we might run into this. The dependency identification fails on test dependencies when using Java 7. Last commit should fix the issue, I'll monitor the CI |
Actually @elharo need you to trigger a build for me. |
Jenkins passed. |
Works similarly to the current logic for getting unused dependencies and declared; looks in output src and test folders and compares what it finds.
Tried to make the test less complicated with only one pom but couldn't get it working.