Community
Participate
Working Groups
While testing shared install scenarios, I noticed the list of software repositories was not "pre-populated" for the normal user, after being installed by administrator. (See bug 322929 for some comments/history). Initially I was using the EPP JEE IDE Package (Helios SR1 RC3 candidate). But then tried "plain" Eclipse SDK, (Helios SR1 RC4) with same result. While initial list is empty, this list becomes populated as expected (sort of) after one site is added to the list (and that site "contacted"). For plain Eclipse SDK, this means after adding http://download.eclipse.org/releases/helios (and clicking "reload") then I could see all sites provided by that site. For the Package, it wasn't quiet the same ... after adding .../webtools/repository/helios, I could then see the 4 sites that are "pre-enabled" for EPP JEE package, which is .../webtools/release/helios, .../eclipse/updates/3.6/, .../releases/helios, .../tools/mylyn/updates/helios. But still did not see the ones that are typically pre-populated, but enabled, in the JEE package. I was testing on Ubuntu 104, 32bit.
Yep, this has nothing to do with EPP and everything to do with p2. From a technical side, when you start in 'shared-install' mode, each user gets their own p2 and configuration folders. We don't pre-populate the list of known update sites with the one from the shared area. This is likely a good idea, but there might be some subtleties that I'm missing.
*** This bug has been marked as a duplicate of bug 249133 ***
