Community
Participate
Working Groups
The director currently fails and exits on unrecognized options. This makes it impossible to use the director application from an existing eclipse install if the eclipse.ini contains any options that were not consumed by the launcher or osgi itself. From http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html, the following options cause the director to fail. (The first two * are present in my install.) -showLocation * -eclipse.password * -eclipse.keyring -registryMultiLanguage -noRegistryCache -noLazyRegistryCacheLoading i didn't try any of the obsolete options, and all the options from 'Others' (ie the workbench) would also cause the director to fail.
I'm not sure I agree with this. This might mean a provisioning request would go through even if some stuff wasn't recognized. Consider something like this... p2director -installFrom x -instalTo y (note the typo) ...the 'instalTo' argument is ignored and the Director decides to default to the same installation. This means my installation will be changed now (which is probably not what I want) and I will be forced to do a revert and probably also use the GC to delete stuff. This might be an extreme example (or maybe I'm misunderstanding the request here) but thought I'd bring it up.
Created attachment 192865 [details] patch Proposed patch adds -showLocation, -eclipse.password and -eclipse.keyring as recognized options that are ignored. Any other unrecognized option remains an error as before.
I released the attach patch. The director still fails on unrecognized options, it just ignores some that it knows about.
