Community
Participate
Working Groups
Compilation and resource copying with projects generated by maven-eclipse-plugin takes about 2 minutes. When opening the projects using m2eclipse (after ditching the .classpath/.project files generated by maven-eclipse-plugin) takes approximately 5x longer, and rebuilds the workspace (according to the progress window) 3-5 times. Due to some plugins we require (jaxb2, javacc for instance) m2eclipse even fails to build our workspace, while it perfectly works when generated by maven-eclipse-plugin. In its current state, m2eclipse is unusable.
I really didn't tell maven to start verifying DTDs, HTML, XML, schemas, run findbugs, etc. so why does m2eclipse insist on adding that to my build?
By default, m2e enables all m2e extensions applicable for a project. So if the project uses pmd and findbugs plugins, m2e will enable integration with corresponding eclipse tooling. You can disable this behaviour for individual maven plugins using special pluginManagement element in pom.xml file (or parent pom). http://wiki.eclipse.org/M2E_plugin_execution_not_covered show how to do it. If this does not solve the problem, please provide standalone sample project and steps to reproduce the problem.
Our project doesn't use pmd, findbugs, etc. So why does it enable those? Why does it enable DTD, schema, HTML checks? There is no setting anywhere to be found in my pom.xml files that tells maven to do so. So m2eclipse is on some sort of quality crusade?
Please provide standalone sample project and steps to reproduce the problem.
Just forget it. I'm fed up with m2eclipse as it is, and apparently there's no real effort on diagnosing the problems—a standard provide a sample project reply.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/