| Summary: | Director should warn and ignore unrecognized options instead of failing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Andrew Niefer <aniefer> | ||||
| Component: | p2 | Assignee: | P2 Inbox <equinox.p2-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | pwebster, remy.suen | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | 3.7 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Niefer
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. |