Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-debug-dev] Debug view entries & termination

Hi Christian,

I believe the issue is that the Launch is never seen as terminated, so
can't be removed.

The default implementation
(org.eclipse.debug.core.Launch.isTerminated()) will never be marked
terminated if no processes or debug targets are ever added.

Therefore EASE needs to implement/override the isTerminated, to do
that you have to instantiate your own ILaunch object, to do so
implement  org.eclipse.debug.core.model.ILaunchConfigurationDelegate2.getLaunch(ILaunchConfiguration,
String) in EaseLaunchDelegate

HTH,
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 13 January 2017 at 11:38, Christian Pontesegger
<christian.pontesegger@xxxxxx> wrote:
> Hi,
>
> EASE is using launch configurations to run scripts within eclipse. Each
> launch creates an active entry in the Debug view, even if 'Run As' is used
> and not 'Debug As'. This seems to be normal behavior as Java launches also
> create these entries.
>
> While those Java entries get terminated and valish automatically after
> termination this does not happen for EASE entries. I guess I need to inform
> the launcher somehow of the termination. How can this be done? I could not
> find API for this on the ILaunch.
>
> thanks
> Christian
>
> _______________________________________________
> jdt-debug-dev mailing list
> jdt-debug-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/jdt-debug-dev


Back to the top