Community
Participate
Working Groups
I create a configuration with the eclipse platform and WST and any needed dependencies. The best way to do this is the download the eclipse runtime binary which doesn't contain JDT. Go to updated manager and install WST and it require dependencies. This configuration doesn't contain JST or JDT. If I only have WST installed and I right click on a HTML file in a Static Web Project, the menu item Run As>>Run On Server doesn't exist. The problem seems to be caused by the fact there is no org.eclipse.debug.ui.actions.ILaunchable defined. There only has to be one defined in any plugin in the configuration. It happens that both JST and JDT have the adapter defined. In ATF I defined a fake entry like the following below to get around the problem. <extension point="org.eclipse.core.runtime.adapters"> <factory class="" adaptableType="org.eclipse.core.resources.IResource"> <adapter type="org.eclipse.debug.ui.actions.ILaunchable"/> </factory> </extension> I wrote this against the server, but maybe wst.web should handle it since that is where the Static Web project deployables are defined. I guess it also could be consider a problem in org.eclipse.debug.
Hi Bob, You're talking about the Run menu not being available at all? If so, then this is an issue between the 'project type' owner and debug. The expected behaviour from platform debug is that the Run menu won't appear unless the resource/selection adapts to ILaunchable. Project owners are responsible for adapting the right objects to make the menu appear, and I'm not sure how/why JDT/JST is providing this for cases they don't handle. I'll transfer to wst.web.
