Community
Participate
Working Groups
We use m2e on a hierachical multi-module maven project (about 100 modules) which also includes more than one web application. We always had problems with m2e (e. g. m2e not recognizing projects as maven modules), but since the recent updates of m2e working is nearly impossible. Symptom: eclipse does not stop "building workspace"; building always turns back to one of the projects (not every time the same) which is earlier in the dependency hierarchy. If this occurs it does not stop doing this. The only solution is to stop eclipse and restart it, otherwise eclipse will end in a OutOfMemory or PermGenSpace exception. This problem occurs - after SVN-updates - after opening or closing projects - after changing code in a project many other projects depend on Especially the last one is a real blocker. We use: - maven 2.2.1 - Eclipse Helios JEE SR1 (Build 20100917-0705) - m2clipse 0.12.1.20110112-1712 with WTP-feature 0.11.1.20101108-1810 (very similar problems with the previous version) in addition - we often have about 20 of the 100 modules of our large maven project opened to avoid unnecessary building in eclipse, but IMO it's one of the main goals of m2e to work in such a way - we have a additional resource-project on the whole maven project to have the whole codebase searchable Our team is looking for other IDEs because maven is out central build tool and it does not work smothly in eclipse the last 2 years.
Although the problem description does not provide enough details to be able to precisely diagnose it, based on other similar problematic workspaces I looked at I believe we addressed the underlying design flaw in m2e 0.13.0. We plan to provide more detailed explanation of the changes that went into 0.13.0 before the release, but in short, there was bad interference between m2e and other workspace builders caused by m2e blindly delegating some workspace operations to Maven. In 0.13.0 m2e only calls into Maven when it is reasonably sure it is safe to do so. It also creates error markers for potentially unsafe but required Maven invocations, so users can adjust their configuration accordingly. In 0.12.x there is something called "custom lifecycle mapping" you may be able to workaround the problem. You can find some info on m2e wiki, but don't hesitate to ask questions on m2e-users mailing list. https://docs.sonatype.org/pages/viewpage.action?pageId=2949459 Feel free to reopen the issue if you still see the problem with recent 0.13.0 builds.
I'm seeing exactly this behavior in a much smaller, multi-module, project using m2e V1.0.0.20110607-2117 on Eclipse 3.7.0. I notice that it has stopped on its own, but it is hard to associate it with any particular reason why. I wish I could give you more information, but it just seems to happen, and then it just stops.
Have you added any lifecycle mappings with execute?
Yes.
That is likely the source of your problem.
I have the same problem with V1.0.0.20110607-2117 on Eclipse 3.7.0. Please reopen or describe how to fix this problem. Really annoying. Makes it nearly impossible to work with eclipse and maven.
Created attachment 200443 [details] Endless Build Jobs This screenshots shows the behavior. If many build jobs and if one job is finished a new one is scheduled immediately.
Anyone can reopen bugs... just make sure to provide enough information for us to troubleshoot the problem, otherwise we won't be able to do anything about the bug regardless of its status. In most cases we'll need complete standalone example project and steps to reproduce the problem. As usual, we welcome quality patches with adequate test coverage. As was noted by Matthew, if you use <execute/> build lifecycle mapping in your project's pom.xml file(s), this is the most likely cause of the endless loop. Remove the mapping to solve the problem.
Sorry three persons sitting now in front of my screen and nobody of us can see anything about how to reopen this bug here... And I think it is very easy to reproduce just make a multi module maven project...
I'll reopen the bug if you attach a standalone sample project (or set of projects) and provide steps to reproduce the problem. (fwiw, you should be able to set status to REOPENED and hit Save Changes)
I just got rid of it by changing the version of the parent in my multi module project. Strange thing is: I can now change it back to the version where the problem occured and the problem doesn`t occur anymore. Very strange... I do not have any <execute/> lifecycle mappings in my parent pom but the parent is not in my workspace. I do have such lifecycle mappings in my multi module project but they seem not to be the problem because I can remove them and the problem is still there. That is everything I can provide because I do not know when the problem occurs and in my case it disappeared magically. But as you can see, others do have the same problem, so just play around with it. I can provide some meta information (versions of maven plugins etc.) if that helps you but I do not know how it should be possible to provide a project where the problem occurs because I have no idea where the problem comes from and also no idea why the problem now disappeared. And I am definetily not able to change the status of the issue here...
@Sascha there have been two reports of endless build loop against m2e 1.0 (so far). One of these appears to be caused by <execute/> mapping and the other cannot be reproduced after some random/noop changes. There is simply not enough information yet to troubleshoot this problem, even if it is caused by m2e.
@Igor: But the problem appears so in my opinion this bug here should be stay open as long as somebody have found a solution for that. Otherwise nobody will care about it and it will be never fixed and it is a really blocker issue.
As I said, bug status does not mean much. If nobody knows what causes the problem or how to reproduce it, there is absolutely nothing we can do about it. And nobody knows if the problem is actually caused by m2e and not some other tool you may have installed.
FWIW: Just encountered this issue, not clear it's the same others have experienced or not. My situation [and what "fixed" it]: Eclipse 3.7.2 / Indigo m2e-scala m2e-wtp Three projects: A [java only, m2e] B [java & scala, m2e, scala-maven-plugin 3.0.2] C [scala only, m2e, scala-maven-plugin 3.0.2] C depends on B depends on A B had an error in a java file - it would not compile successfully. Eclipse began cyclic/never-ending-build loop of C [build, rebuild, rebuild, etc] Cycle broken when: 1. Fixed error in java file in B 2. Forced rebuild of B 3. Pulled up "progress tab" and "canceled" all existing "building" tasks [a few..]. Eclipse initiated one last build of C... and cycle didn't restart. Prior to (3) I watched the builds-in-progress, and didn't notice the list growing shorter. I'm not confident enough on this point to make a firm statement. [BTW, I don't see anyway to reopen this bug, nor am I sure that's the right thing to do at this point]
I have had this problem too (m2e 1.3.1.20130219-1424). The culprit was a project which had the maven2Builder twice in the builders list (.project file): <projectDescription> <name>xxx</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.wst.common.project.facet.core.builder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.wst.validation.validationbuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.m2e.core.maven2Builder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.m2e.core.maven2Builder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.m2e.core.maven2Nature</nature> <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.maven.ide.eclipse.maven2Nature</nature> <nature>org.eclipse.wst.common.project.facet.core.nature</nature> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature> <nature>com.atlassw.tools.eclipse.checkstyle.CheckstyleNature</nature> <nature>net.sf.eclipsecs.core.CheckstyleNature</nature> <nature>org.zeroturnaround.eclipse.jrebelNature</nature> </natures> </projectDescription> Removing one of the build entries solved the problem.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
