Re: [m2e-dev] How to handle conflicting lifecycle mappings

[Olivier NOUGUIER <olivier.nouguier@xxxxxxxxx>]

Hi,
 There is a notion of secondary configurator [1] that can run after their primaries. In your secondary configurator you will have to check the pom dependencies.

HIH

[1] https://github.com/cheleb/m2eclipse-wtp-gdt/blob/master/org.maven.ide.eclipse.gdt/org.maven.ide.eclipse.gdt.core/plugin.xml#L40

On Wed, Sep 21, 2011 at 8:19 PM, Andrew Eisenberg <andrew@xxxxxxxxxxxx> wrote:

Hi all,

We have 2 m2e configurators that need to run on the same maven plugin
at the same goals.  This does not seem possible since m2e sees the
conflict as incompatible and is turning both of them off.

Some more information.  Both are attached to the aspectj plugin.  The
first one must always be run (it is the AJDT configurator).  And the
second one should only be run if there is a particular dependency
specified in the pom.xml.  Is there any way to handle this?

thanks,
Andrew
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

-- 
"Computers are useless. They can only give you answers."
- Pablo Picasso -