[news.eclipse.tools.jdt] Ideas on JVMTI Profiling of JUnit suites (throu

[Stephane Mikaty <stephane@xxxxxxxxxx>]

Hi everyone,

As I'm just starting in plugin development, i thought it would save
me some time and frustation to share with you what I'm trying to do.

I'm trying to integrate the JUnit plugin launch configuration type
with a plugin of mine that starts the JUnit test runner with extra
options on the command line to load a JVMTI agent i wrote.
This involves appending one entry to the bootclasspath and adding
an agentlib option to the vm arguments. After some research, i figured
the Eclipse Way (tm) would be to implement a launch delegate:

<extension point="org.eclipse.debug.core.launchDelegates">
<launchDelegate id="com.mikaty.leakdog.eclipse.LeakdogProfileDelegate"
   delegate="com.mikaty.leakdog.eclipse.LeakdogProfileDelegate"
   type="org.eclipse.jdt.junit.launchconfig"
   modes="profile"/>
</extension>

Now, my launch delegate is in every way identical to the junit one,
except for the extra options that i want to add. I was hoping to just
extend the junit launch delegate, override the method that returns the
bootclasspath, the method that returns vm arguments, and be done with 
it. So i went on:

import org.eclipse.jdt.internal.junit.launcher.JUnitLaunchConfiguration;

public class LeakdogProfileDelegate extends JUnitLaunchConfiguration

And here is the first bump in the road, the junit launch delegate 
belongs to an "internal" package, which I'm not supposed to depend on, 
as the rules of good plugin citizenship mandate.

The reason I'm posting this is, I'm not even sure I'm going about the 
problem the right way. Am i using the right extension point?

Thanks in advance,

Stephane