Skip to content
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

Merged
merged 7 commits into from
Jul 11, 2020

Conversation

ian-lavallee
Copy link
Contributor

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.

@ian-lavallee
Copy link
Contributor Author

@elharo

@ian-lavallee ian-lavallee requested a review from elharo July 10, 2020 18:54
Copy link
Contributor

@elharo elharo left a 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:

https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/foo/lastCompletedBuild/testReport/

Only fails on a couple of nodes, but it does look related

@ian-lavallee
Copy link
Contributor Author

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

@ian-lavallee
Copy link
Contributor Author

Actually @elharo need you to trigger a build for me.

@elharo
Copy link
Contributor

elharo commented Jul 11, 2020

Jenkins passed.

@elharo elharo merged commit 6d3aa86 into apache:master Jul 11, 2020
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