Community
Participate
Working Groups
I have Eclipse plug-ins which instrument a device with extra logging. They must instrument the device before the debugging session starts. This involves adjusting some configuration files and installing some DLLs. Hence I need some API or extension point in order to install an "action" to do this task, before launch. Launch must not proceed until the task is complete. I can probably make do with the existing launch listener interface. However, there are also others who want to get a chance to perform a task before the launch occurs. Hence Ken Ryall proposes that there should be a more general "launch action" mechanism. This would let me define any action that might need to take place before a launch. An extra tab would be provided in the launch configuration interface, to allow the user to enable, disable or reorder these launch actions. The user would get a chance to add certain simple launch actions from within the user interface - for example, running a batch file or shell script - but more complex ones would be defined programmatically by extending a new extension point.
I'll work with Adrian to see if we can satisfy his requirements with something in M6.
I've been working on a generic 'Launch Action' framework in conjunction with Marthin Oberhuber of DSDP/TM fame which matches almost exactly what you describe (we even called them Launch Actions!). The buck is currently with our legal team so that I can contribute the code, but I'll keep you posted on any developments via this bug. Robert
I've run out of time to look at this for CDT 4.0, will plan for next time.
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.
