Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 29971 - context specific arguments to run/debug launchers
Summary: context specific arguments to run/debug launchers
Status: RESOLVED DUPLICATE of bug 10035
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Jared Burns CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-22 09:13 EST by Kari Ikonen CLA
Modified: 2003-05-27 09:34 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 Kari Ikonen CLA 2003-01-22 09:13:17 EST 
Let's assume that I've utility class A within my project which
takes as an parameter name of some other class, and performs
something based on that.

I would like to be able to define generic context specific
arguments for A within its' launch-script. So something like "${resource.fullpath}", which would expand into fullpath of
the currently selected resource.
Comment 1 Darin Wright CLA 2003-01-22 10:31:14 EST 
Not planned for 2.1. This is a request for generic variables added to the debug 
platform to be used for any kind of launch config.
Comment 2 Darin Wright CLA 2003-05-26 16:14:51 EDT 
We are planning to support "launch variables" in 3.0.
Comment 3 Darin Wright CLA 2003-05-26 16:15:14 EDT 
Jared, can this one be marked as a duplicate?
Comment 4 Jared Burns CLA 2003-05-27 09:34:58 EDT 
Definitely.

*** This bug has been marked as a duplicate of 10035 ***