Eclipse maven plugin updating indexes

I think I saw this problem couple of weeks ago but it went away after I ran "mvn clean package" from command line and refreshed from eclipse.-- Regards, Igor --------------------------------------------------------------------- To unsubscribe from this list, please visit: On a related note, I'm often getting stuck in an endless "building workspace" step now which seems to be related to the maven plugin.I don't see any reason why it should have to load all my POMs and update dependencies when I restart, which is what it seems to be doing.

eclipse maven plugin updating indexes-68

If so, please read note in installation reqs page [1] or better update to Subclipse 1.4 If you see this with Subclipse 1.4, can you take a thread dump of Eclipse JVM process [2] and send it to us.

Thanks Eugene [1] Requirements#Installation Requirements-Install Subclipse[2] FAQ#Project FAQ-Howtogenerateathreaddump--------------------------------------------------------------------- To unsubscribe from this list, please visit: Hello Guys, Surprisingly I'm facing the same problem but couldn't able to get away with it:( I'm new to ESB Maven with Eclipse world so please help me resolve this problem.

I'm wondering if it might have to do with me switching my project to use target/ instead of target-eclipse/.

My hunch is that this is somehow related to me running maven on the command line as well. Dan Why is the m2e plugin always updating my dependencies all the time?

Especially for fixing bugs it is crucial that the developers can reproduce your problem.

For this reason, entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated. Contributors can check out the project from our source repository and will find supplementary information in the guide to helping with Maven.

My hunch is that this is somehow related to me running maven on the command line as well. Do you have repeatable way to reproduce endless build?

I think I saw this problem couple of weeks ago but it went away after I ran "mvn clean package" from command line and refreshed from eclipse. Although I did not have so much tpme to dig it in, if m2eclipse and subversion is used together in the same work space then startup initialization ends up with deadlocks, both trying to acquire semaphores.

The posts to the mailing list are archived and could already contain the answer to your question as part of an older thread.

Tags: , ,