Re: [m2e-dev] Maven Updates

[<paul.warren@xxxxxxx>]

Hi Igor,

Thanks for the info.  So it makes sense it is optimized for incremental development.  And we have plugged into your incremental builder to do some extra "stuff" relevant to the lifecycle of our projects but that isn't particularly relevant here.

So I guess the key sentence there was that m2e never updates snapshots unless explicitly requested by the user.

And I am taking that to mean that the <snapshots><updatePolicy>always</updatePolicy></snapshots> specification in the project's pom.xml is effectively redundant and ignored for any maven invocation performed by m2e right?

Thanks,
_Paul

-----Original Message-----
From: m2e-dev-bounces@xxxxxxxxxxx [mailto:m2e-dev-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: Thursday, February 02, 2012 2:39 PM
To: m2e-dev@xxxxxxxxxxx
Subject: Re: [m2e-dev] Maven Updates

m2e is optimized for frequent workspace incremental builds (i.e. the
most typical Eclipse IDE usage pattern) and in order to achieve
acceptable performance we had to decompose Maven build into more basic
components and execute individual components when they are needed.

At all times m2e maintains registry of all workspace maven projects and
their dependencies. The registry is updated every time one of workspace
pom.xml file changes or if the user explicitly request maven project
update. m2e never updates snapshots unless explicitly requested by the user.

In additional to dependency information, project registry also maintains
cache of MavenProject instances. The cache is lazily populated, but the
same MavenProject instance is reused by workspace build and other
operations until m2e detects the instance needs to be updated.

m2e uses lifecycle mapping configuration to determine how to configure
Eclipse workspace projects and what parts of Maven build lifecycle
should be executed as part of Eclipse workspace build. m2e never
executes complete maven build lifecycle inside Eclipse JVM. Wiki [1]
provides some additional information about lifecycle mapping.


[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered

--
Regards,
Igor

On 12-02-02 4:24 PM, paul.warren@xxxxxxx wrote:
> Hi Guys,
>
> Wondering if you might be able to answer this for me.
>
> We are building an IDE for our platform on top of eclipse and m2e.
>
> When a user of our IDE creates an application project, that project's
> pom.xml specifies a snapshot update policy of "always".
>
> Now from the maven documentation I believe this means maven will check
> for newer snapshots every time it is started.
>
> What I am trying to figure out is when does m2e "start" maven. Is it
> just for Run As/Debug As invocations? Does it include maven incremental
> builder invocations? Does m2e force a check during start-up of
> eclipse/m2e plugins themselves?
>
> Thanks in advance
>
> _Paul
>
>
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev