Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319160 - [target] Using an Eclipse installation as target platform, config.ini/osgi.configuration.area is not respected
Summary: [target] Using an Eclipse installation as target platform, config.ini/osgi.co...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-07 12:55 EDT by Martin Oberhuber CLA
Modified: 2019-09-09 02:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2010-07-07 12:55:17 EDT
Build ID: Eclipse 3.6

Preferences > PDE > Target Platform : Add : Start with Empty : Add Installation

The org.eclipse.pde.internal.ui.shared.target.EditProfileContainerPage
dialog has a flag "This install uses the default configuration area".

But if my Eclipse installation uses a configuration/config.ini file which defines the osgi.configuration.area variable as something different, that setting is not picked up. I believe that the setting should be picked up, because otherwise it is very hard to get my install correctly set up as target platform.

In my understanding "nonstandard config area" is anything that I specify as -configuration on a commandline. But the setting specified in config.ini should be parsed and understood by the wizard.

For the records, my config.ini uses
osgi.configuration.area=@user.home/.workbench-3.2.0.20100701-0951/configuration
Comment 1 Curtis Windatt CLA 2010-07-07 14:30:06 EDT
The default configuration area is <install>/configuration.  We do not read the config.ini.  Changing this report to an enhancement request.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:37:14 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 3 Julian Honnen CLA 2019-09-09 02:32:34 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.