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
