Re: [m2e-users] excessif dependency resolving before launching a main

[Clément Guillaume <clement@xxxxxxxxxxxxx>]

I found this potentially related ticket https://bugs.eclipse.org/bugs/show_bug.cgi?id=563742

On Thu, Jun 4, 2020 at 5:49 PM Clément Guillaume <clement@xxxxxxxxxxxxx> wrote:

Hello

I have noticed, after upgrading to eclipse 2020-03, that it takes more time between the moment I trigger a main method to run and the moment it starts running (even when there is no code change in between multiple run).

Using the "Maven console" in the "Console view", i see way more "Resolving ...." log than before.

I think the more project dependencies your project has the more log there is.

For example, I open the datarouter projects in eclipse.

https://github.com/hotpads/datarouter

I added a hello world main in the CopyTableService class.

https://github.com/hotpads/datarouter/blob/master/datarouter-copy-table/src/main/java/io/datarouter/plugin/copytable/CopyTableService.java

I counted the number of log line for each version of eclipse between the time I trigger the run and the beginning of the run.

in eclipse 2019-12 (m2e 1.14.0.20191209-1925), 51 lines (3 for each dependency of the project)

in eclipse 2020-03 (m2e 1.15.0.20200310-1832), 468 lines:

• 51 similar to 2019-16 (with "with classifier null to")
• 417 additional lines (with "with classifier  to")

also 468 lines in eclipse 2020-06-M2

I attached the logs here https://drive.google.com/drive/folders/1YLgyq6juuf1_eLTub1H_B2l-jmz6WSIY?usp=sharing

I have noticed the same extra processing before launching a testng test.

What caused this regression?

Is it possible to revert that or configure eclipse to reduce those processing?

Why are some processing necessary in between multiple runs of the same unmodified code?

Thanks, Clément Guillaume