installing additional eclipse indigo files

user963070 picture user963070 · Mar 31, 2012 · Viewed 13.1k times · Source

After downloading Eclipse Indigo on a clean pc, when I try to download from http://dl.google.com/eclipse/plugin/3.7 and download SDKs and Google Plugin , at about 35% of the way through I start getting errors.

Install download1
An internal error occurred during: "Install download1".
Comparison method violates its general contract!

Install download2
An internal error occurred during: "Install download1".
Comparison method violates its general contract!

Install download3
An internal error occurred during: "Install download1".
Comparison method violates its general contract!

Installing Software
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Multiple problems occurred while downloading.
Unable to write to repository: file:/C:/Users/erice/Downloads/eclipse-jee-indigo-win32-x86_64/eclipse/.
C:\Users\erice\Downloads\eclipse-jee-indigo-win32-x86_64\eclipse\plugins\com.ning.async-http-client_1.6.3.201112281337.jar (Access is denied)
Unable to write to repository: file:/C:/Users/erice/Downloads/eclipse-jee-indigo-win32-x86_64/eclipse/.
C:\Users\erice\Downloads\eclipse-jee-indigo-win32-x86_64\eclipse\plugins\com.ning.async-http-client_1.6.3.201112281337.jar (Access is denied)
No repository found containing: osgi.bundle,org.eclipse.m2e.archetype.common,1.0.200.20111228-1245
No repository found containing: osgi.bundle,org.eclipse.m2e.maven.indexer,1.0.200.20111228-1245
No repository found containing: osgi.bundle,org.eclipse.m2e.maven.runtime,1.0.200.20111228-1245
No repository found containing: osgi.bundle,org.jboss.netty,3.2.4.Final-201112281337

Any clues?

Answer

Kane picture Kane · Mar 31, 2012

It's a known issue of Eclipse 3.7 running on Java 7.

Possible workarounds:

  • use JRE7u5 (last version)
  • when using JRE7, theres a small rarely documented feature set system property java.util.Arrays.useLegacyMergeSort=true This should use old implementation and should not bring up the bug (I haven't tested, but you can search for the property ;-) )

See bug 317785 for detail.