-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[MNG-7677] Maven slowness improvement #989
[MNG-7677] Maven slowness improvement #989
Conversation
The change is effectively in resolver 1.9.5, but there are other "low hanging fruits" like delegate created on a "hot method". --- https://issues.apache.org/jira/browse/MNG-7677
This PR will pass once apache/maven-resolver#245 is merged, built and deployed by Jenkins, and artifacts picked up by this PR. |
After apache/maven-resolver#245 merged (and deployed by CI), restarted all the CI jobs on this PR, and they are expected to pass OK, as wrote above. |
Of the resolver (downloading vs downloaded), just report after the fact it was downloaded (or failed to download), no need for double lines for same resource/dependency. This experiment includes apache#989 but does not affects it (just to create "closer" Maven to upcoming release). As one could expect, IT suite does fail with this change as some ITs do assert against the build logs (but the build itself did pass OK). Failing ITs: [ERROR] Failures: [ERROR] MavenITmng6240PluginExtensionAetherProvider.testPluginExtensionDependingOnMavenAetherProvider:83->AbstractMavenIntegrationTestCase.assertEquals:668->AbstractMavenIntegrationTestCase.assertEquals:673 expected: <2> but was: <0> [INFO] [ERROR] Tests run: 885, Failures: 1, Errors: 0, Skipped: 80 As to be expected, the IT asserts there is log line without progress (so DownloadING one, the one that is removed).
So this need to be a singleton? |
I'd rather say: given this class is stateless, it CAN be singleton/shared/reused, instead to be re-instantiated for each call of this "hot" method. |
I see, makes sense. No reason to create new objects all the time. |
The crux was in resolver 1.9.5, but there are other "low hanging fruits" like delegate created on a "hot method". --- https://issues.apache.org/jira/browse/MNG-7677
The crux was in resolver 1.9.5, but there are other "low hanging fruits" like delegate created on a "hot method".
https://issues.apache.org/jira/browse/MNG-7677