m2e invokes configuratots in the order of their corresponding maven plugin executions. If groovy comes before compiler, then groovy configurator will be called before java configurator.
Benson Margulies <[email protected]> wrote: >M2e works fine when the groovy configurator plugin I've adapted isn't >there. Somehow, the presence of that configurator causes trouble. > >What controls the order in which things run? Could this just be the >groovy thing running *first* instead of *second*? > > > >On Mon, May 30, 2011 at 6:04 PM, Fred Bricon <[email protected]> wrote: >> I'm curious to see what specific settings make the eclipse compiler >> unsupported. Will take a look, someday :-) >> >> 2011/5/30 Igor Fedorenko <[email protected]> >>> >>> compilerId=eclipse is not currently supported, somebody has to write >a >>> project configurator for it. But otherwise, mapping is done for >specific >>> value of compilerId parameter, so it is possible to have two >separate >>> mappings and m2e will pick one of the other based on project >>> configuration. >>> >>> -- >>> Regards, >>> Igor >>> >>> On 11-05-30 05:55 PM, Fred Bricon wrote: >>>> >>>> Igor, >>>> >>>> how do you would you configure the lifecycle mapping to use the >>>> javaConfigurator for compilerId=javac OR compilerId=eclipse ? >>>> >>>> regards, >>>> >>>> Fred Bricon >>>> >>>> 2011/5/30 Igor Fedorenko <[email protected] >>>> <mailto:[email protected]>> >>>> >>>> Java nature is enabled based on presence of >maven-compiler-plugin with >>>> compilerId=javac in project build lifecycle (see [1] for exact >>>> mapping). >>>> >>>> Configuration logic is implemented in [2], which is meant to be >>>> extensible, but I don't know if there is enough flexibility to >support >>>> groovy projects. If not, you'd have to implement java nature and >>>> classpath setup logic in GroovyProjectConfigurator. >>>> >>>> [1] >>>> >>>> > http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.jdt/lifecycle-mapping-metadata.xml >>>> [2] >>>> >>>> > http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.jdt/src/org/eclipse/m2e/jdt/internal/AbstractJavaProjectConfigurator.java >>>> >>>> -- >>>> Regards, >>>> Igor >>>> >>>> >>>> On 11-05-30 05:23 PM, Benson Margulies wrote: >>>> >>>> No, this isn't zen. >>>> >>>> I'm trying to help out the maintainer of the groovy >maven/eclipse >>>> plugins in adapting to 0.13. >>>> >>>> Their configuration looks like: >>>> >>>> public class GroovyProjectConfigurator extends >>>> AbstractProjectConfigurator >>>> implements IJavaProjectConfigurator { >>>> ... >>>> >>>> } >>>> >>>> When I load everything in with 0.13, a test project never >acquires >>>> java nature, and then their configuration fails because >there's no >>>> classpath. >>>> >>>> Is >>>> >>>> > org.codehaus.groovy.m2eclipse.GroovyProjectConfigurator.configure(ProjectConfigurationRequest, >>>> IProgressMonitor) responsible for adding the Java nature? >>>> >>>> _______________________________________________ >>>> m2e-users mailing list >>>> [email protected] <mailto:[email protected]> >>>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>>> >>>> >>>> >>>> >>>> -- >>>> "Have you tried turning it off and on again" - The IT Crowd >>>> >>>> >>>> >>>> _______________________________________________ >>>> m2e-users mailing list >>>> [email protected] >>>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >>> _______________________________________________ >>> m2e-users mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> >> >> -- >> "Have you tried turning it off and on again" - The IT Crowd >> >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> >_______________________________________________ >m2e-users mailing list >[email protected] >https://dev.eclipse.org/mailman/listinfo/m2e-users -- Sent from my SGS _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
