Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326494

Summary: Support '#' comments in vm arguments on launch configuration
Product: [Eclipse Project] PDE Reporter: Michael Woski <woskimi>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: ankur_sharma, curtis.windatt.public, marco
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

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.