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

["Tami Takamiya" <ttakamiy@xxxxxxxxxx>]

Igor Fedorenko wrote following in the original
thread (http://dev.eclipse.org/mhonarc/lists/m2e-users/msg05095.html):

> I don't believe increasing the
cache size or making it user-configurable is the right answer here. We
need to stop Eclipse from running the build (if that's what it's doing)
and maybe cache project runtime classpath such that m2e does not need to
read MavenProjects during application launch. 

I agree with Igor that we needed to
stop Eclipse from running the build (I think that's happening) and the
increasing the cache size would be just a workaround.

The problem is that I do not have enough
skills to debug the m2e code to figure out why the build runs when it shouldn't...
 That's why I keep using the workaround.

Tami Takamiya



From:      
 Mickael Istria <mistria@xxxxxxxxxx>
To:      
 m2e-dev@xxxxxxxxxxx
Date:      
 06/16/2016 05:36 AM
Subject:    
   Re: [m2e-dev]
Better performace of m2e and some doubts about thecode
Sent by:    
   m2e-dev-bounces@xxxxxxxxxxx

---

On 06/15/2016 10:26 PM, Tami Takamiya wrote:
We have been using a locally patched
version of m2e.core plugin (project buffer size was incresed from 5 to
5,000 in ProjectRegistryManager.java) and it gives us much better performance.
Do you think it would be possible to find some heuristic
for this value, based on the VM heap size for example? It would be nice
to have m2e computing a value that gives a better speed/resources trade-off.
-- 
Mickael Istria
Eclipse developer at JBoss,
by Red Hat
My
blog - My
Tweets_______________________________________________
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