Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 122930 - Error when downloading features/plugins to a read-only instance of Eclipse
Summary: Error when downloading features/plugins to a read-only instance of Eclipse
Status: RESOLVED DUPLICATE of bug 108191
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Update-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-06 11:28 EST by Maxime Daniel CLA
Modified: 2006-02-17 09:04 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxime Daniel CLA 2006-01-06 11:28:55 EST
Using build I20051215-1506 under Linux.
Having installed Eclipse into /opt/eclipse_32_M4/eclipse, under root, without
granting write access to it to my usual user id.
The following steps lead to an error (stack trace below):
- connect an launch Eclipse under my usual user id;
- select an update site and a feature that is new for the considered instance
  of Eclipse;
- accept the terms of the license agreement;
- do not change the Install Location, click Finish;
- once the download is complete and presented with the feature verification (here
  I am using an unsigned feature), click Install;
- get an error:

Error 2006-01-06 17:26:26.920 An internal error occurred during: "Update Manager".
java.lang.ClassCastException
at org.eclipse.update.internal.core.SiteFileContentConsumer.abort(SiteFileContentConsumer.java:209)
at org.eclipse.update.internal.core.FeatureExecutableContentConsumer.abort(FeatureExecutableContentConsumer.java:160)
at org.eclipse.update.core.Feature.install(Feature.java:538)
at org.eclipse.update.internal.core.SiteFile.install(SiteFile.java:74)
at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:122)
at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:86)
at org.eclipse.update.internal.operations.InstallOperation.execute(InstallOperation.java:72)
at org.eclipse.update.internal.operations.BatchInstallOperation.execute(BatchInstallOperation.java:84)
at org.eclipse.update.internal.ui.wizards.InstallWizard2.install(InstallWizard2.java:373)
at org.eclipse.update.internal.ui.wizards.InstallWizard2.access$1(InstallWizard2.java:370)
at org.eclipse.update.internal.ui.wizards.InstallWizard2$1.run(InstallWizard2.java:464)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

Adding write access to the directory solves the problem.

Note also that along the Change Install Location path, things are quite
better because Eclipse detects that the installation location is read only, 
and provides a neat message to tell the user so.
Comment 1 Leif Frenzel CLA 2006-01-06 11:39:49 EST
From the stacktrace, this looks to me the same problem as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=108191
Comment 2 Maxime Daniel CLA 2006-01-06 11:50:41 EST
(In reply to comment #1)
> From the stacktrace, this looks to me the same problem as in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=108191

Agree. Should have searched more thoroughly.
Comment 3 Pascal Rapicault CLA 2006-02-17 09:04:10 EST

*** This bug has been marked as a duplicate of 108191 ***