Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #345078 +++ Unpacking a fresh Eclipse SDK 3.7M7 I selected for installation: http://download.eclipse.org/releases/indigo Then I picked "Eclipse XML Editors and Tools" This constantly triggers the following error: An error occurred while collecting items to be installed session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Artifact not found: osgi.bundle,org.eclipse.wst.common.emfworkbench.integration,1.2.100.v201011172300. http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse/releases/indigo/201105060900/aggregate/plugins/org.eclipse.wst.common.emfworkbench.integration_1.2.100.v201011172300.jar.pack.gz Given that the file exists on the server this at first looks like a problem with the mirror. However, then all mirrors seem to be affected. I've seen it also with these mirrors: http://ftp.wh2.tu-dresden.de/pub/mirrors/eclipse http://ftp.halifax.rwth-aachen.de/eclipse//releases http://mirror.selfnet.de/eclipse/releases http://artfiles.org/eclipse.org//releases Could be a bug in p2 or the aggregation but it only affects this one plug-in. For completeness: in the .log it looks like this: java.io.FileNotFoundException: http://artfiles.org/eclipse.org//releases/indigo/201105060900/aggregate/plugins/org.eclipse.wst.common.emfworkbench.integration_1.2.100.v201011172300.jar.pack.gz at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:384) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:358) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:295) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:80) at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:130) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:586) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:569) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:641) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:260) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:235) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:191) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:122) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:625) at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
I've been able to duplicate the original bug report, starting with eclipse M7 SDK, and using the /releases/indigo site. Note that if I specify -Declipse.p2.mirrors=false when I startup, it will work ... that is, find the artifacts on download.eclipse.org. I thought even without -Declipse.p2.mirrors=false that p2 should "fall back" to download.eclipse.org ... or, that is, the "original" repo artifact site it started with? Granted, there is an error that causes this artifact, and one other, to not be mirrored anywhere ... seems that should not completely "block" an install. Any ideas? p2 bug? something wrong with artifact repo?
I ran into this over the week end and opened bug #345061. What is surprising to me is that the mirrors being contacted are all missing the artifacts we are looking for. I have not investigated how far behind those mirrors are, but there is definitely something fishy going on. Could someone look into this? I'm totally max'ed out on corporate commitments and other p2 committers are sick or have new babies. Thx.
(In reply to comment #2) > ... > What is surprising to me is that the mirrors being contacted are all missing > the artifacts we are looking for. I have not investigated how far behind those > mirrors are, but there is definitely something fishy going on. > Could someone look into this? Yes ... that's all explained in the original bug this was cloned from, bug 345078 ... just to cross reference ... in short, artifacts with the word "integration" in them are not mirrored; haven't been for years. The webmasters will look to remove (or change?) their heuristic ... but, the idea has been to protect (many) mirrors from getting weekly integration builds, and for (most of them) to get just milestones and releases. Normally, there are always a few mirrors that do, intentionally, ask to "mirror everything" but it just so happens that the 40 that have Indigo M7 so far do not (as of Sunday, 11 PM) ... hence, bug shows up. Also, but doesn't show up if -Declipse.p2.mirrors=false (which can be used as a work around, until fixed). *** This bug has been marked as a duplicate of bug 345061 ***
