Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319960 - [frameworkadmin] EclipseLauncherParser does not recognize Java options
Summary: [frameworkadmin] EclipseLauncherParser does not recognize Java options
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-15 05:21 EDT by Stefan Stern CLA
Modified: 2019-05-30 16:50 EDT (History)
0 users

See Also:


Attachments
Patch containing fix, Unit-test and test-data (7.62 KB, patch)
2010-07-15 05:43 EDT, Stefan Stern CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Stern CLA 2010-07-15 05:21:48 EDT
Build Identifier:  I20100608-0911

If the launcher.ini defines the configuration folder with the argument -configuration, then the Parser will set the proper value. If the according Java property is set (osgi.configuration.area), then this option is ignored and instead the default "configuration" is used. 

Result is, that e.g. the P2 director application will fail, if trying to install an IU into a product which defines its configuration location not by using -configuration but using -vmargs and -Dosgi.configuration.area.

Reproducible: Always
Comment 1 Stefan Stern CLA 2010-07-15 05:27:19 EDT
I got a patch ready, including a fix and a UNIT Test to verify the solution. But I can't create a patch atm, as CVS always breaks with the message "connection reset". 

I will try later again
Comment 2 Stefan Stern CLA 2010-07-15 05:43:16 EDT
Created attachment 174380 [details]
Patch containing fix, Unit-test and test-data
Comment 3 Eclipse Genie CLA 2019-05-30 16:50:00 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.

--
The automated Eclipse Genie.