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
