Community
Participate
Working Groups
Originally reported as https://issues.sonatype.org/browse/MNGECLIPSE-2320 If the Maven Builder is disabled in the project builder list and then the Maven->Update Project configuration action is executed, another Maven builder gets added to the List, the other builder stays disabled in the list and cannot be removed with an eclipse function, just by modifying the .project file.
Vote: Disabling maven builder in a project is very useful feature and m2e should respect that setting. Since maven does always full build, it can be much more slower than eclipse build and when the "Build Automatically" option is selected, this build runs on every save action. This is really slowing down development. We solve this by disabling the maven builder, but sometimes Maven builder is reborned in a new incarnation. Currently this is blocking our way to use hierarchical structure for multimodule projects, since there is no way to simply import them into eclipse workspace as eclipse projects. Maven project import, on the other hand, triggers this involuntary reconfiguration.
To be clear, "maven does always full build" is a separate problem. If it still happens with recent m2e 0.13 builds, please open new bugreport and provide sample standalone project and steps to reproduce the problem.
Fixed: http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=95d32e7bd1ce9883e5df59218b9ee061ece2fccc https://github.com/sonatype/m2e-core-tests/commit/b693aa49b892613a6c41152045cf5c26259de9d7
Implementation uses internal classes from org.eclipse.core.externaltools. Need to evaluate if we want to take the risk of using internal classes this deep in m2e core.
Removed the changes that added dependencies on internal eclipse classes: http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=0d2fb47b89cdd49d6be6e11fa56f437347a91785
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
