Community
Participate
Working Groups
One of the biggest pains I have with the M2eclipse plugin is that every time I save a change to a java file it triggers a maven build. This perhaps wouldn't be a huge issue if it didn't suddenly make any other operation in eclipse impossible until the build completes. In my experience it also causes downstream projects to be rebuilt too and that can take a long time. In my experience using M2eclipse with build automatically set to true makes the tooling impossible to use. I lose all productivity gains I might have made by using maven and eclipse. The problem is if I set build automatically to false I don't know until I hit the command line if I broke something. When using the eclipse ant integration a save doesn't cause an ant build to run automatically. I can cause this to occur if I wish, but it certainly isn't the default. I don't care if you choose to fix this by providing an option to disable it, but with the current behaviour m2eclipse is useless.
Eclipse workspace build integration has been reworked in m2e 0.13.0 and we are not aware of any cases when saving .java file triggers Maven build. Please reopen this bug and provide sample project we can use to reproduce the problem, if it still happens in recent 0.13.0 builds.
Recent build can be found at: http://download.eclipse.org/releases/indigo or http://download.eclipse.org/technology/m2e/updates/M
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
