Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326494 - Support '#' comments in vm arguments on launch configuration
Summary: Support '#' comments in vm arguments on launch configuration
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-29 04:27 EDT by Michael Woski CLA
Modified: 2019-01-15 04:38 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Woski CLA 2010-09-29 04:27:47 EDT
Build Identifier: M20100909-0800

Hi,

my workbench launch configuration contains some parameters/vm arguments that I sometimes un-/comment, using normal '#' syntax. The equinox launcher can handle that just fine. However, when I create an Eclipse launch configuration inside the workbench, it takes the runtime's vm arguments as template, including my commented lines. This in return causes the classloader to choke because it gets told to load a class something like #-blabla, which of course doesn't exist.
It took me some time to check where the problem came from, and it is easily solved. However, I think I might forget again ... So maybe this could be solved at its root?

bye Michi

Reproducible: Always
Comment 1 Marco Descher CLA 2019-01-15 04:38:07 EST
That would be really helpful. Another possible solution might be to provide a boolean_prompt variable, with a simple question on whether a specific argument should be included.