Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 218874 - [prov] VM arguments should be in config.ini
Summary: [prov] VM arguments should be in config.ini
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 M6   Edit
Assignee: Pascal Rapicault CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-13 16:04 EST by John Arthorne CLA
Modified: 2008-02-28 11:17 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2008-02-13 16:04:15 EST 
We set various VM arguments in eclipse.ini:

-Dorg.eclipse.equinox.simpleconfigurator.useReference=true
-Dorg.eclipse.update.reconcile=false
-Dorg.eclipse.p2.update.compatibility=false

If these properties are missing when self-hosting with p2, things are horribly broken. Simple configurator doesn't use reference URLs, so all bundles are copied by the framework on startup.  If automatic updates downloads new plugins, update.configurator attempts to install them and the IDE blows up because it is not dynamic. In short, these properties are absolutely critical. I spent several hours this week trying to figure out why things were breaking for me, because I had added a VM argument on the command line last week for doing YourKit profiling. Perhaps these arguments should be added in config.ini instead of eclipse.ini so they won't get lost if vm arguments are added on the command line.
Comment 1 Pascal Rapicault CLA 2008-02-28 11:17:23 EST 
On Andrew's suggestion I have created a setProgramProperty command who causes the property to be written in the config.ini.
This is released in HEAD.