Yup, sorry, seems I broke something.

Anyway, I won't be able to investigate until the next couple weeks. So
don't hesitate to take a look at the code and submit  Gerrit patches[1]

[1]
https://www.eclipse.org/m2e/documentation/m2e-development-environment.html


On Fri, Jul 3, 2015 at 4:26 PM, Max Rydahl Andersen <[email protected]>
wrote:

> Open a Bugzilla with info and link it to the issue fixed in 1.6.1 then
> anyone can investigate.
>
> Fred is on pto right now so will be a bit before he can help fix it.
>
> /max
> http://about.me/maxandersen
>
>
> > On 03 Jul 2015, at 19:30, Vincent Vandenschrick <[email protected]>
> wrote:
> >
> > Further investigation shows that the problem actually arises between m2e
> 1.6.0 and m2e 1.6.1. As there is a single bug fixed for this release, I
> suppose this change is the reason of the conflict :
> >
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=471038 : Configurator is
> not called if secondary for a goal, but also primary for another goal
> >
> > As I understand it, I have now 2 configurators for the
> maven-compiler-plugin activated that are in conflict (?) : the one that I
> explicitly install to cope with groovy-eclipse-compiler, and another
> default configurator coming from m2e itself.
> >
> > Might be that before this fix, only the groovy-eclipse-compiler
> configurator was activated. Any option for solving this issue ?
> >
> > I found a very similar question on SOF :
> http://stackoverflow.com/questions/31135002/update-to-m2e-1-6-resulted-in-conflicting-lifecycle-mapping-error
> , but this is on the war plugin execution.
> >
> > Any hint ? Of course, I can provide a sample project if needed.
> >
> > Kind regards,
> > Vincent
> >
> >> Le 3 juil. 2015 à 18:01, Vincent Vandenschrick <[email protected]> a
> écrit :
> >>
> >> By the way, It says "conflicting" lifecycle mapping. Is there a way to
> know the details about the conflict ? Is it logged somewhere ?
> >>
> >> Vincent
> >>
> >>
> >>> Le 3 juil. 2015 à 17:34, Vincent Vandenschrick <[email protected]> a
> écrit :
> >>>
> >>> Thanks for your answer Igor. You are right, m2e integration is done
> through the Groovy-Eclipse configurator for m2Eclipse (
> http://docs.groovy-lang.org/latest/html/documentation/tools-groovyeclipse.html#Groovy-EclipsecompilerpluginforMaven-Groovy-Eclipseconfiguratorform2Eclipse).
> So I suppose that something has changed that makes it incompatible.
> >>>
> >>> Regards,
> >>> Vincent
> >>>
> >>>
> >>>> Le 3 juil. 2015 à 17:12, Igor Fedorenko <[email protected]> a
> écrit :
> >>>>
> >>>> m2e never provided out-of-the-box support for
> >>>> compilerId=groovy-eclipse-compiler, so I don't know how it worked with
> >>>> m2e 1.5. you probably want to ask among groovy users and/or
> developers.
> >>>>
> >>>> --
> >>>> Regards,
> >>>> Igor
> >>>>
> >>>>> On Fri, Jul 3, 2015, at 10:59 AM, Vincent Vandenschrick wrote:
> >>>>> Hi all,
> >>>>>
> >>>>> After upgrading to M2E 1.6 on Luna, I'm facing a weird problem.
> >>>>>
> >>>>> M2E reports errors on my projects complaining about :
> >>>>>
> >>>>> Conflicting lifecycle mapping (plugin execution
> >>>>> "org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (execution:
> >>>>> default-compile, phase: compile)"). To enable full functionality,
> remove
> >>>>> the conflicting mapping and run Maven->Update Project Configuration.
> >>>>>
> >>>>> and :
> >>>>> Plugin execution not covered by lifecycle configuration:
> >>>>> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (execution:
> >>>>> default-compile, phase: compile)
> >>>>>
> >>>>>
> >>>>> Same for the testCompile goal.
> >>>>>
> >>>>>
> >>>>>
> >>>>> The fact is that I've overridden the compile goal with the following
> >>>>> definition in order to leverage the groovy-eclipse-compiler :
> >>>>>
> >>>>>  <plugin>
> >>>>>       <groupId>org.apache.maven.plugins</groupId>
> >>>>>       <artifactId>maven-compiler-plugin</artifactId>
> >>>>>       <version>${compiler-plugin.version}</version>
> >>>>>       <configuration>
> >>>>>         <compilerId>groovy-eclipse-compiler</compilerId>
> >>>>>         <source>${java.version}</source>
> >>>>>         <target>${java.version}</target>
> >>>>>         <encoding>UTF-8</encoding>
> >>>>>         <!-- set verbose to be true if you want lots of uninteresting
> >>>>>         messages -->
> >>>>>         <!-- <verbose>true</verbose> -->
> >>>>>       </configuration>
> >>>>>       <dependencies>
> >>>>>         <dependency>
> >>>>>           <groupId>org.codehaus.groovy</groupId>
> >>>>>           <artifactId>groovy-eclipse-compiler</artifactId>
> >>>>>           <version>${groovy-eclipse-compiler.version}</version>
> >>>>>         </dependency>
> >>>>>         <dependency>
> >>>>>           <groupId>org.codehaus.groovy</groupId>
> >>>>>           <artifactId>groovy-eclipse-batch</artifactId>
> >>>>>           <version>${groovy-eclipse-batch.version}</version>
> >>>>>         </dependency>
> >>>>>       </dependencies>
> >>>>>   </plugin>
> >>>>>
> >>>>> Everything ran smoothly on M2E 1.5. Of course, the necessary
> >>>>> configurators are installed to take care of the
> groovy-eclipse-compiler.
> >>>>>
> >>>>> Thanks in advance for any help,
> >>>>>
> >>>>> Vincent
> >>>>> _______________________________________________
> >>>>> m2e-users mailing list
> >>>>> [email protected]
> >>>>> 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
> >>>> [email protected]
> >>>> 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
> > [email protected]
> > 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
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>



-- 
"Have you tried turning it off and on again" - The IT Crowd
And if that fails, then http://goo.gl/tnBgH5
_______________________________________________
m2e-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to