Since I have many of Maven projects
in my development workspace, the sum of these "reading times"
can be larger.
It looks like the MavenImpl#readMavenProject
method is used to read Maven projects and actual builds (or something very
time-consuming) take place eventually when projects have dependencies on
some projects loaded in Eclipse workspace.
When the build was already done, I also
assume reading projects should be completed almost immediately.
m2e-users-bounces@xxxxxxxxxxx wrote on 06/11/2015
> From: Igor Fedorenko <igor@xxxxxxxxxxxxxx> > To: m2e-users@xxxxxxxxxxx > Date: 06/11/2015 09:35 AM > Subject: Re: [m2e-users] Maven project cache
size in ProjectRegistryManager > Sent by: m2e-users-bounces@xxxxxxxxxxx >
> m2e 1.4 almost certainly won't run on eclipse 4.4 due to some
> changes in equinox iirc. and more generally, we only test m2e with
> single target eclipse version, so m2e 1.5 was tested with eclipse
> 4 and m2e 1.6 with eclipse 4.5. > > as for classpath caching, that was just an example,
I will really
> need to understand why launching is slow for your project before we
> can discuss how to make it fast. as far as I can tell, this works
> well for vast majority of users. > > -- > Regards, > Igor