Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311947 - [launcher] Better handling of missing non-optional arguments
Summary: [launcher] Better handling of missing non-optional arguments
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Launcher (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-06 14:29 EDT by Andrew Niefer CLA
Modified: 2021-08-27 13:21 EDT (History)
0 users

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 Andrew Niefer CLA 2010-05-06 14:29:45 EDT 
Most of the arguments the launcher uses (-startup, --launcher.library, etc) have a non-optional value that needs to be specified (-startup launcher.jar)

By inspection, it appears that if a non-option value is missing from the command line:
-startup --launcher.library foo.so
then the argument parsing for -startup will incorrectly remove the next arg from the list, which will result in generally broken arguments.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:33:04 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 2 Eclipse Genie CLA 2021-08-27 13:21:02 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.