Re: [m2e-users] Maven project cache size in ProjectRegistryManager

[Tami Takamiya <ttakamiy@xxxxxxxxxx>]

Igor,

Thank you for your quick response.

Previously we were using m2e 1.4 (1.4.1.20140328-1905)
on Eclipse 3.8.1 and upgraded to m2e 1.6 (1.6.0.20150325-2013) on Eclipse
4.4.2.
I have not tried to run m2e 1.4 on Eclipse
4.4.2.  I will try that today to see whether it would resolve our
issues.

I really like the idea to cache project
runtime classpath!

Tami Takamiya

m2e-users-bounces@xxxxxxxxxxx wrote on 06/11/2015
07:37:47 AM:

> From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
> To: m2e-users@xxxxxxxxxxx
> Date: 06/11/2015 07:38 AM
> Subject: Re: [m2e-users] Maven project cache
size in ProjectRegistryManager
> Sent by: m2e-users-bounces@xxxxxxxxxxx
> 
> The actual cache size is rather arbitrary, but m2e intentionally 
> keeps the number of cached MavenProject instances very small and 
> there is no way to configure the cache size. Eclipse is not expected
> to build anything before application launch, so the behaviour you
> observe unusual.
>  
> The limit on project cache size was introduced
very early in m2e 1.5
> development cycle, so unless you are upgrading from m2e 1.4 or 
> earlier, something else must be going on.
>  
> 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. 
>  
> --
> Regards,
> Igor
>  
>  
> On Thu, Jun 11, 2015, at 12:04 AM, Tami Takamiya
wrote:
> Hi, 
>  
> This is my first post to this group.  I
was not sure if I should 
> post to the user group or the developer group.  Since I am an
user, 
> I post this here.  If it seems more appropriate in the developer
> group, I will re-post it. 
>  
> ==== 
>  
> We have a performance issue with using m2e (version
1.6.0.
> 20150325-2013).  It seems like whenever we run a program or a
JUnit,
> lots of projects in workspace are rebuilt and stuck at 57% with the
> "Verifying launch attributes..." message. 
>  
> I ran a separate Eclipse instance in debug mode
and found there is a
> cache in 
> org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager
> class and it seems to be used for caching dependency information of
> each Maven project. 
>  
> However, according to the source code, the maximum
size of the 
> project cache is hard-coded to 5, which I think too small for our
usage.   
>  
> Is there any way to increase this value?  
Or is this value set to 5
> intentionally?   
>  
> ==== 
>  
> Tami Takamiya
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> To change your delivery options, retrieve your
password, or 
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>  _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users