Bug 288688 - [P2] default update sites don't come up in read-only shared install
Summary: [P2] default update sites don't come up in read-only shared install
Status: CLOSED DUPLICATE of bug 249133
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-04 19:44 EDT by Gergely Nagy CLA
Modified: 2009-09-04 19:52 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 Gergely Nagy CLA 2009-09-04 19:44:27 EDT 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061212 Iceweasel/3.0.12 (Debian-3.0.12-1)
Build Identifier: M20090828-0800

After installing 3.5.0 - 3.5.1RC2 in a read-only directory (a.k.a. "shared install", e.g. on Linux: /usr/local/eclipse), the P2 update site lists are empty.
It should contain the default one for Galileo and platform updates (http://download.eclipse.org/releases/galileo and http://download.eclipse.org/eclipse/updates/3.5 I think).

Reproducible: Always

Steps to Reproduce:
1. have an Eclipse 3.5.x install in a read-only directory (e.g /usr/local/eclipse on Linux)
2. start eclipse as a user
3. go to Preference | Install/Update | Available software -> the list is empty
4. try to install new software -> nothing will found by default



This used to work on 3.3 and probably in 3.4.
Also, it does work if you install Eclipse in user's home (or any dir with write access).
Workaround: add the sites manually. Hint: use Ekke's list: http://ekkescorner.wordpress.com/eclipse/update-sites. Could not find anything as useful at eclipse.org.
Comment 1 Gergely Nagy CLA 2009-09-04 19:48:44 EDT 
The problem is there on 3.6M1 as well.
Comment 2 Remy Suen CLA 2009-09-04 19:52:35 EDT 

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