GMaven should not cause m2eclipse to add extra classpath entry

As described on the eclipse-plugin-dev mailing list, GMaven is adding an extra classpath entry to eclipse .classpath files when there are references between groovy and java files. From the mailing list:

====================

Removing the .classpath entry should not be a problem - the new Groovy plugin doesn't need it. The entry is likely added when m2eclipse is asked to update project configuration and it goes through the various plugin goals that are bound to the "generate-sources" phase (as is the GenerateStubsMojo). This goal has a method getOutputDirectory() that returns this path.

/**

• Generate Java stubs from Groovy sources.
  *
• @goal generateStubs
• @phase generate-sources
• @requiresDependencyResolution compile
• @since 1.0-beta-2
  *
• @version $Id: GenerateStubsMojo.java 8 2009-07-16 09:15:04Z user57 $
• @author <a href="mailto:jason@planet57.com">Jason Dillon</a>
  */
  public class GenerateStubsMojo
  extends AbstractGenerateStubsMojo
  {
  /**
• The directory where generated Java stub files will be placed.
  *
• @parameter default-value="$ {project.build.directory}

  /generated-sources/groovy-stubs/main"

• @required
• @noinspection UnusedDeclaration
  */
  private File outputDirectory;

protected List getProjectClasspathElements() throws DependencyResolutionRequiredException

protected File getOutputDirectory()

....