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

Performance functional-bug fix for the Maven-plugin #736

Merged
merged 3 commits into from
Nov 16, 2020

Conversation

barmakoWS
Copy link
Contributor

Upgraded org.codehaus.plexus:plexus-utils to its latest version (3.3.0) to resolve long directory scanning times for the maven plugin.

Resolves #729

@nedtwigg
Copy link
Member

Have you used https://github.com/diffplug/spotless/blob/main/CONTRIBUTING.md#maven to integration test this? I might be wrong, but I would expect https://github.com/diffplug/spotless/blob/main/plugin-maven/src/test/resources/pom-build.xml.mustache to need changes as well.

@nedtwigg nedtwigg merged commit e2d51d5 into diffplug:main Nov 16, 2020
@nedtwigg
Copy link
Member

Published in plugin-gradle 5.8.2 and plugin-maven 2.6.1.

@barmakoWS
Copy link
Contributor Author

Yeah, I followed the instructions and tested it manually.
The automated tests failed due to another issue that was already fixed (#737 ). I re-checked it now, and they pass.

From looking at the generated pom, it doesn't seem that pom-build.xml.mustache needs to be updated (it makes a direct dependency to plexus-utils:3.3.0)

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.

Maven scanning time issue for big projects
2 participants