-
Notifications
You must be signed in to change notification settings - Fork 212
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
1.0.0-m1 slower than 0.8.2 #758
Comments
Scanning for projects... takes ~10 seconds even when I am in a directory where there is just a single project. |
|
I'm aware of the problem, and no this is not really acceptable imho. I raised MNG-7647. |
Do you mean a directory that is part of a multi-module project, but has no child modules? Or do you mean a directory that has a single project, i.e. not part of multi-module project? |
Yes, exactly this. |
Thanks for clarifying. I'm wondering if there's a measurable difference if you disable build/consumer POM decoupling. From MNG-6656, it should be possible to disable that with |
I haven't pinpoint the exact problem, however mvnd 1.0.0-m1 is noticeably slower than 0.8.2. More significant, running |
When building Camel Quarkus with these changes apache/camel-quarkus#4355 in place using
1.0.0-m1 is slower than 0.8.2 by more than 10 seconds.
At the first sight the initial scanning of Maven modules takes much longer. It is ~9 seconds with 0.8.2, but ~19 sec with 1.0.0-m1.
Is this expected, @gnodet ?
The text was updated successfully, but these errors were encountered: