Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331593 - [engine] Profile points to wrong install folder
Summary: [engine] Profile points to wrong install folder
Status: RESOLVED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-01 14:33 EST by Katya Stoycheva CLA
Modified: 2020-02-23 05:35 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katya Stoycheva CLA 2010-12-01 14:33:50 EST
Build Identifier: I20101028-1441

Roaming attribute of the profile is disregarded when the profile is not "self". If there was no previous self-update, which to trigger replacement of the org.eclipse.equinox.p2.installFolder's value with the actual destination, this causes installing IUs at a wrong place.

Reproducible: Always

Steps to Reproduce:
1. Unzip Eclipse in a folder of your choise without starting it. 
2. Try to update it with a new feature using other Eclipse.
3. Note that the installed feature won't be placed in the chosen Eclipse destination. You can find the feature under the file path hardcoded in the profile as install folder (which is actually the path dependent on the build machine used to build Eclipse.zip)
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:10:46 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Ed Merks CLA 2020-02-23 05:35:01 EST
I don't believe this is current an issue.