Community
Participate
Working Groups
Please take a look at #126594 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=126594) We are developing profiling plugin for Eclipse and we've encountered problem similar to bug above. We are trying to provide org.eclipse.debug.core.launchDelegates extension point with customized GenericServerLaunchConfigurationDelegate subclass for "profile" mode. But current implemetation blocks our attempt to override "profile" mode. Existing extension point provides all three modes: "run, debug, profile" and our custom delegate is never called. In https://bugs.eclipse.org/bugs/show_bug.cgi?id=126594#c16 Tim deBoer says that new extension point "org.eclipse.jst.server.core.serverProfilers" is introduced to support server profiling, but we cannot use this extension point and provide our additional vmArgs inside "plugin.xml" because the command line highly depends on current run configuration and can't be defined as a static constraint. We'are suggesting to improve existing GenericServerLaunchConfigurationDelegate API so that it would be possible to override "profile" mode. We are hoping you'll help us like for issues #77566, #116844, #88642, Best regards, Vitaly PImenov.
In Eclipse 3.2 and earlier there could only be one launch delegate per launch mode (per config type). In 3.3, we are enhancing the launch framework to allow more than one launch delegate per mode, and allow the user to choose the tooling they want to use. This is a new feature in 3.3. Marking as dup. *** This bug has been marked as a duplicate of 157059 ***
