Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327824 - Add development launching arguments to product configuration editor
Summary: Add development launching arguments to product configuration editor
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.0   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-14 15:55 EDT by Patrick Paulin CLA
Modified: 2019-09-09 02:32 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Paulin CLA 2010-10-14 15:55:24 EDT
Build Identifier: 

Many RCP developers use the Product Configuration editor to generate Run Configurations when developing with the PDE. The only downside to this is that we often want to use different arguments when developing and when shipping a product. Examples:

* -consoleLog when developing but not when shipping
* specialized VM args for memory usage, etc.

If I put development-time arguments in the product, I need to remember to restore them whenever I do a build. If I leave the build-time arguments in the product, then I need to modify the Run Configurations generated by the product. It's also easy to overwrite these modifications by running from the Product Configuration Editor a second time.

My suggestion is that another tab be added to the Launching Arguments section. The tab could be labelled "Development" and would contain the arguments to use when generating a Run Configuration. If these were empty, then fall back to the normal arguments.


Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:14:18 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 Julian Honnen CLA 2019-09-09 02:32:50 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.