Eclipse updating maven dependencies stuck

Default Index Updater.access0(Default Index at org.apache.maven.index.updater.Default Index Updater$Lucene Index Index File(Default Index at org.apache.maven.index.updater.But why it takes bloody ages while this thread runs with high priority? iostat shows it takes up to 80% of IO and CPU bandwidth and brining performance of my machine to its knees. Updating does not seem to work, and shows the following error message: Id=4.5.1.M20150904-0015 java.version=1.8.0_66 java.vendor=Oracle Corporation Boot Loader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.product org.eclipse.m2e.logback.appender Error Tue Jan 12 CET 2016 Unable to update index for central| Index Output.write String(Index at org.apache.lucene.index. Segment Info.write(Segment at org.apache.lucene.index. Segment Infos.write(Segment at org.apache.lucene.index. Segment Infos.prepare Commit(Segment at org.apache.lucene.index. Index Writer.start Commit(Index at org.apache.lucene.index. Index Writer.commit(Index at org.apache.lucene.index. Index Writer.close Internal(Index at org.apache.lucene.index. Index Writer.close(Index at org.apache.lucene.index. Index Writer.close(Index at org.apache.maven.index.context. Nexus Index Writer.close(Nexus Index at org.apache.maven.index.context.

The mytest project is shown here with the red x icons indicating that there are problems with the project. The maven SW "eclipse:eclipse" goal will download any necessary dependencies and will update our project's .classpath to include these dependencies.Now, I'll create an External Tool configuration so that I can run the maven eclipse:eclipse goal in Eclipse. I would have used a : instead of a ~ but Eclipse doesn't allow colons in the name field. The Working Directory is an Eclipse variable that specifies the currently selected project's location in the file system.I'll create the configuration with the following features. The Arguments field specifies "eclipse:eclipse", the maven goal that we'd like to execute. First, I assumed that the "developers" list was for those developing Maven as opposed to those developing USING Maven. By any chance does anyone know why when I installed the 3.0.5 release of the Spring Framework (with its 3.6 Eclipse developer tools suite) that any time a new project is created (or one of Spring's sample projects is loaded) Maven tries to update its dependencies, but gets stuck in a never-finished state that locks up the Eclipse editor forever? Shot in the dark here but hopefully someone has some ideas.I have posted in the Spring forums (along with a few others) but so far no luck. --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] I faced a similar issue some times.