Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Where does Java nature come from?


how do you would you configure the lifecycle mapping to use the javaConfigurator for compilerId=javac OR compilerId=eclipse ?


Fred Bricon

2011/5/30 Igor Fedorenko <igor@xxxxxxxxxxxxxx>
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.



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

Is org.codehaus.groovy.m2eclipse.GroovyProjectConfigurator.configure(ProjectConfigurationRequest,
IProgressMonitor) responsible for adding the Java nature?
m2e-users mailing list

"Have you tried turning it off and on again" - The IT Crowd

Back to the top