Cannot run a profile launching configuration on Eclipse 3.1

othomann · Post by **othomann** » Fri Oct 01, 2004 3:02 pm

Trying to use YourKit3.0 on top of Eclipse 3.1, I got the following error:

java.lang.NoSuchMethodError: org.eclipse.pde.internal.ui.launcher.LauncherUtils.getPrimaryFeatureId()Ljava/lang/String;
at com.yourkit.eclipsePlugin.YkWorkbenchLaunchConfigurationDelegate.if(a:86)
at com.yourkit.eclipsePlugin.YkWorkbenchLaunchConfigurationDelegate.for(a:354)
at com.yourkit.eclipsePlugin.YkWorkbenchLaunchConfigurationDelegate.launch(a:32)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:569)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:720)
at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:892)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

This means the yourKit Eclipse plugin is using an internal method from the pde.ui plugin. This is strictly forbidden in the recommended usage of Eclipse API. Only API methods can be called.

Hope this will help you to fix this issue.

Best regards,

rkosta · Post by **rkosta** » Sat Oct 02, 2004 10:34 pm

Well, I can understand why they use internal API, there are just no other good way to launch runtime workbench.
But I also would like to have version that works under 3.1 M2...

Post by **Vladimir Kondratyev** » Sun Oct 03, 2004 6:56 am

We are using internal Eclipse API just because public API is not enough to implement workbench launching. But we are going to track the changes in internal Eclipse API and issue bugfix builds in time. Most probable plug-in for Eclipse 3.1-M1 will be available in version 3.0.1 of YourKit Java Profiler.

rkosta · Post by **rkosta** » Sun Oct 03, 2004 7:06 am

Why only for M1? M2 is already published.

Post by **Vladimir Kondratyev** » Mon Oct 04, 2004 7:00 am

Strange, there is only 3.0.1 at http://www.eclipse.org/downloads. Where can I download 3.1-M2?

rkosta · Post by **rkosta** » Mon Oct 04, 2004 7:21 am

3.0.1 is bug fix for 3.0

3.1 M2 is build for 3.1 version with new features.

http://download2.eclipse.org/downloads/ ... /index.php

othomann · Post by **othomann** » Mon Oct 04, 2004 2:08 pm

Internal code should never be used. This is clearly against the portability and maintability of Eclipse plugins. If you miss something like an API to start a runtime workbench, you should request it on the Eclipse bugzilla site. This is the way to go. The internal code can be completely refactored without a notice.
It is possible to workaround this issue with 3.1 using a Java program launching configuration. It works fine.
Hope you can solve this by using only APIs, otherwise this prevents a nice integration inside Eclipse.