Re: [m2e-dev] Better performace of m2e and some doubts about the code

[carsten.pfeiffer@xxxxxxxx]

You might have a look at http://dev.eclipse.org/mhonarc/lists/m2e-users/msg05095.html
and see if increasing the cache size
helps.

It does help us (with > 100 projects
in the workspace).

Cheers
Carsten



From:      
 Fabio Bohnenberger
<fabio.jose.bohnenberger@xxxxxxxxx>
To:      
 "m2e-dev@xxxxxxxxxxx"
<m2e-dev@xxxxxxxxxxx>
Date:      
 14.06.2016 02:52
Subject:    
   [m2e-dev] Better
performace of m2e and some doubts about the code
Sent by:    
   m2e-dev-bounces@xxxxxxxxxxx

---

I was looking to the m2e update project mechanism, trying
to figure out where it could be more performatic.

Understanding better how does the process run, I could see that the update
Maven project process run in few steps(refresh,update project configuration
and clean), an the most "slow" is the refresh.

The refresh step is basically composite by:
1. Updates the projects GAV and caching MavenProjects with the MavenProjectFacade.
2. Updates of the dependencies, capabilities and lifecycle mapping of the
projects

Both the two steps make a ProjectBuilder.build(from maven API) call, that
uses a lot of disk usage in my opinion. So I wanted to know, what was the
motivation to implement the refresh process in two steps. Couldn't the
process just use one ProjectBuilder.build?

But, even that the refresh process was implemented with just one ProjectBuilder.build,
when we select more projects to have the configuration updated, we will
have this number of calls to the ProjectBuilder.build, that can result
on a slow process for big projects with many modules.
One possible solution would be to make just one call with all the projects
that should be build, using the ProjectBuilder.build( List<File>
pomFiles, ... ) method.

I want to improve the process performace in some way, but before start
coding I think that is important to understand clearly why are update maven
project process implemented the way it is today. Maybe can anyone explain
me better the maven project update process? Any opinions about the possible
solutions I proposed?_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev