1) Some networking issue in Ubuntu caused there is no response from DNS (probably). There are also other scenarios, but the result of some runtime problem is that Indigo hangs.
2) This is from the workspace log: !SESSION 2011-07-13 11:29:33.251 ----------------------------------------------- eclipse.buildId=I20110613-1736 java.version=1.6.0_26 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product -clean !ENTRY org.eclipse.core.resources 2 10035 2011-07-13 11:30:17.293 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.mylyn.tasks.ui 4 0 2011-07-13 11:30:42.312 !MESSAGE Could not load repository template extension contributed by org.sonar.ide.eclipse.mylyn.ui with connectorKind jira !ENTRY org.sonar.ide.eclipse.logback.appenders 4 0 2011-07-13 11:31:49.668 !MESSAGE Unable to update index for central|http://repo1.maven.org/maven2 !STACK 0 java.io.IOException: Connect times out at org.eclipse.m2e.core.internal.index.nexus.AsyncFetcher$PipedErrorInputStream.checkError(AsyncFetcher.java:253) at org.eclipse.m2e.core.internal.index.nexus.AsyncFetcher$PipedErrorInputStream.read(AsyncFetcher.java:259) at java.io.PipedInputStream.read(PipedInputStream.java:361) at java.io.InputStream.read(InputStream.java:85) at java.util.Properties$LineReader.readLine(Properties.java:418) at java.util.Properties.load0(Properties.java:337) at java.util.Properties.load(Properties.java:325) at org.apache.maven.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:457) at org.apache.maven.index.updater.DefaultIndexUpdater.access$100(DefaultIndexUpdater.java:75) at org.apache.maven.index.updater.DefaultIndexUpdater$IndexAdaptor.setProperties(DefaultIndexUpdater.java:607) at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:788) at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:135) at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1124) at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager.updateIndex(NexusIndexManager.java:1081) at org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager$1.run(NexusIndexManager.java:658) at org.eclipse.m2e.core.internal.index.nexus.IndexUpdaterJob.run(IndexUpdaterJob.java:71) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.net.ConnectException: Connect times out at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.doConnect(NettyAsyncHttpProvider.java:853) at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.execute(NettyAsyncHttpProvider.java:731) at com.ning.http.client.AsyncHttpClient.executeRequest(AsyncHttpClient.java:484) at com.ning.http.client.SimpleAsyncHttpClient.execute(SimpleAsyncHttpClient.java:285) at com.ning.http.client.SimpleAsyncHttpClient.get(SimpleAsyncHttpClient.java:202) at org.eclipse.m2e.core.internal.index.nexus.AsyncFetcher.retrieve(AsyncFetcher.java:205) at org.apache.maven.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:452) ... 9 more 3) After that I can interact with the Eclipse, but only until any operation starts in Progress. Than hangs and even UI does not response. I have to kill the process. 4) Another scenario is when I close some dependency of a project. One problem was the pmd extension, but after it's uninstallation it is still not completely away. At this time I don't know how to reproduce it. I think that maybe somewhere in the code is catched a RuntimeException and it is not handled completely well. Can someone check it? Thanks, David Matějček. _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
