Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358803 - Error when trying to update to Eclipse IDE for Java EE Developers 1.4.1.20110909-1818
Summary: Error when trying to update to Eclipse IDE for Java EE Developers 1.4.1.20110...
Status: CLOSED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-24 10:38 EDT by orthodox.mich CLA
Modified: 2011-09-24 20:09 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description orthodox.mich CLA 2011-09-24 10:38:11 EDT 
Build Identifier: 20110615-0604

Error when trying to update to Eclipse IDE for Java EE Developers 1.4.1.20110909-1818

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=).
No repository found containing: osgi.bundle,org.eclipse.help.base,3.6.1.v201109091335
No repository found containing: osgi.bundle,org.eclipse.jdt.debug,3.7.1.v20110802_r371
Problems downloading artifact: osgi.bundle,org.eclipse.jdt.launching,3.6.1.v20110803_r371.
File has invalid content:C:\Users\mich\AppData\Local\Temp\signatureFile5143428702756007914.jar
Invalid content:lib/launchingsupport.jar
The file "lib/launchingsupport.jar" in the jar "C:\Users\mich\AppData\Local\Temp\signatureFile5143428702756007914.jar" has been tampered!

Reproducible: Always

Steps to Reproduce:
1. Check for updates
2. Choose Eclipse IDE for Java EE Developers 1.4.1.20110909-1818
Comment 1 Pascal Rapicault CLA 2011-09-24 20:09:25 EDT 
This indicates a problem with either the transfer (pb downloading the bytes from the server) or with the file on the server. Try downloading again and it is likely to work, as I just did a complete update and did not reproduced the issue.