Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 282740

Summary: addRepository settings absent for non-Admin users on Vista
Product: [Eclipse Project] PDE Reporter: Michael Sacarny <michael.sacarny>
Component: BuildAssignee: pde-build-inbox <pde-build-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P3    
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Whiteboard:
Attachments:
Description Flags
Built example of p2 Self-update RCP Mail (SDKUI.exe) none

Description Michael Sacarny CLA 2009-07-07 15:44:54 EDT
Created attachment 140996 [details]
Built example of p2 Self-update RCP Mail (SDKUI.exe)

Build ID: I20090611-1540

Steps To Reproduce:
1.Download "Reusing the Eclipse SDK UI in its entirety" example as per http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application.
2.Build via Product, Export.
3.Install in Program Files subfolder on Vista.
4.Start sdkui.exe as user without elevating to Admin. 
5.Select Window, Preferences, Install/Update, Available Software Sites.
6. Observe the list of sites is empty.
7. Now run sdkui.exe as Admin.
8. Observe site list includes 'http://www.eclipse.org/equinox/p2/testing/updateSite'.   


More information:
The update site _is_ visible on XP installs.

I got into this because I could not get my update sites to show for Vista, even when building with p2.inf colocated with Product files in headless builds. See:
http://www.eclipse.org/newsportal/article.php?id=1829&group=eclipse.platform.pde#1829

The problem occurs for 3.4-style use of Director builds, when p2.inf is colocated with manifest file, and even Exported builds, as in SDK UI example.

Absence of intended update sites interferes with product maintenance and ease-of-use. I'm attaching my build of the SDK UI example built with 3.5.
Comment 1 John Arthorne CLA 2009-07-10 17:06:08 EDT
When you install into Program Files on Vista, this creates what we call a "shared install" because regular users are not allowed to write there. It's a known limitation that repository settings (profile preferences in general) from the base install are not currently cascaded to child installs in multi-user installs.

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