[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] m2e-dev Digest, Vol 22, Issue 1
|
I am surprised m2e calls AbstractMavenLifecycleParticipant, this is not
intentional. AbstractMavenDependencyResolver.resolveProjectDependencies
is the only way that may work. I suggest you run the code through
debugger to see how m2e reads MavenProject instance and configures
workspace projects. There were noticeable changes in 1.1, so you almost
certainly want to look at the new version.
--
Regards,
Igor
On 11-12-01 2:59 PM, Christopher Hunt wrote:
Hi Igor,
Thanks for the reply. To respond:
On 02/12/2011, at 2:49 AM, m2e-dev-request@xxxxxxxxxxx
<mailto:m2e-dev-request@xxxxxxxxxxx> wrote:
m2e does not directly execute Maven build lifecycle, so
AbstractMavenLifecycleParticipant will not be called be default, at
least I do not believe it will.
Actually, I think it does... may be because it is part of Maven's pom
loading machinery? Dependencies added by my participant are shown in
Eclipse.
However the resource folders my participant adds are not recognised...
Any further ideas? I want my participant to inform m2e that it is part
of the project configuration cycle.
Thanks.
Kind regards,
Christopher
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
