-
Notifications
You must be signed in to change notification settings - Fork 56
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
[MPLUGIN-526] Clean up dependencies reported by dependencies:analyze #287
Conversation
Guys, please have a look. If all fine, I'd like to start the vote today. |
@michael-o I still have a bunch of warnings when running
|
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.
There are still lots of warnings when running the dependency:analyze
goal.
I am aware if that, I have intentionally left out deprecated modules and test dependencies because many of those are false positives. We last a test-runtime scope. Do you still want me to tackle test scope? |
No, not necessarily. I'm fine with leaving out deprecated modules and test dependencies.
Should those be ignored too ? |
Here we have two issues:
output:
for Lines 38 to 44 in 993425c
|
@michael-o @gnodet should we cherry-pick to 3.x branch? |
If the 3.x branch is active, we should, but I should that @gnodet would reset 3.x as as soon as he will bump master to 4.0.0. |
I've reset the 3.x branch to the current master (just after the release). |
Perfect, thanks. Let's wait until the vote has passed and then we can continue with your open PRs. |
This closes #287