Eclipse Helios無法安裝m2e

Question

我對Maven非常陌生。我試圖在Eclipse Marketplace（eclipse-jee-helios-SR1-win32）中從Eclipse Marketplace安裝m2e插件。我的Eclipse文件夾位於c:\（c:\eclipse）。它會正確下載並安裝它（至少看起來如此！），然後要求重新啓動Eclipse。我確實重新啓動它。但是一旦它重新啓動，就開始下載了一些東西，我得到以下錯誤：

eclipse.buildId=M20100909-0800 
java.version=1.6.0_18 
java.vendor=Sun Microsystems Inc. 
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US 
Framework arguments: -product org.eclipse.epp.package.jee.product 
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product 


Error 
Fri May 27 11:17:41 EDT 2011 
Unable to update index for central|http://repo1.maven.org/maven2 

java.io.IOException: An existing connection was forcibly closed by the remote host 
at org.maven.ide.eclipse.internal.index.AsyncFetcher$PipedErrorInputStream.checkError(AsyncFetcher.java:181) 
at org.maven.ide.eclipse.internal.index.AsyncFetcher$PipedErrorInputStream.read(AsyncFetcher.java:188) 
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.sonatype.nexus.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:498) 
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.access$100(DefaultIndexUpdater.java:74) 
at org.sonatype.nexus.index.updater.DefaultIndexUpdater$IndexAdaptor.setProperties(DefaultIndexUpdater.java:780) 
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:954) 
at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:138) 
at org.maven.ide.eclipse.internal.index.NexusIndexManager.updateRemoteIndex(NexusIndexManager.java:1072) 
at org.maven.ide.eclipse.internal.index.NexusIndexManager.updateIndex(NexusIndexManager.java:1025) 
at org.maven.ide.eclipse.internal.index.NexusIndexManager$1.run(NexusIndexManager.java:632) 
at org.maven.ide.eclipse.internal.index.IndexUpdaterJob.run(IndexUpdaterJob.java:71) 
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host 
at sun.nio.ch.SocketDispatcher.read0(Native Method) 
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25) 
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233) 
at sun.nio.ch.IOUtil.read(IOUtil.java:200) 
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236) 
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:322) 
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281) 
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201) 
at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
at java.lang.Thread.run(Thread.java:619) 

有沒有人有任何想法，這是什麼？我重複了這個過程三次，重複了全新安裝的Eclipse，同樣的問題。我的同事使用相同版本的Eclipse，並且完成了相同的過程。他能夠在< 1分鐘內安裝m2e！這太令人沮喪了！

編輯1：

我已經配置在Eclipse Network ConnectionsProxy Settings和這些設置是爲我的同事們工作的罰款。所以我猜這不是代理問題。

Answer 1

實測值簡單的解決方案。只是做了Eclipse的更新，它的工作！

Answer 2

儘管最近公共Maven地址本身不再可瀏覽，但這更可能是由於Eclipse中的設置不正確。

請參閱this answer設置您的代理，如果您有代理，更一般地，請檢查Eclipse同事的「網絡連接」設置，以確保您擁有相同的代理。

---

有關信息/存檔，關於browse status of http://repo1.maven.org/maven2：

The raw browsing ability was originally removed to prevent automatic web crawler/scraper activity from de-stabilizing the Central servers.
Some of that ability has been returned.
It is currently possible to browse at levels deeper than the root , /org , /com , and /net.

So, if you try to navigate to http://repo1.maven.org/maven2/org , for example, you will see a static page with a link to the appropriate Browse view on http://search/maven.org .
However, if you go even one level deeper, to http://repo1.maven.org/maven2/org/apache , the standard directory browse functionality will be in place.