dfht

Alternatively, separating the maven configurator into a separate (optional) feature would of course achieve the same goal as I can then choose which projects I want the nature on rather...

When I start the server I get info logs like this in the error log: GWT: possiblyLaunchGwtSuperDevModeCodeServer: Launching GWT Super Dev Mode CodeServer. launcherId=06413077-5ba1-4ca7-ba52-00434129ef07 launcherDir=I:\NeonTest4\adyptable\Workspaces\J\AdyptWebGenerated\AdyptWebMain\wtpServerGen\Servers\Adypt_Tomcat_7.0\deploy\wtpwebapps\AdyptWebMain But the launcher it refers...

Oh well it was just a thought..... It might well not be this. I tried changing the code server to an absolute path: So in the code server launcher arguments...

I checked out the video [https://www.youtube.com/watch?v=LtH4KzmguL0&ab_channel=BrandonDonnelson] where it said that you don't even need to set the -launcherDir in the code server, so clearly it can't use that to try...

In the logs, when it claims it is about to start the launcher, it is definitely identifying the correct one as well, as the launcherId it logs is the same...

Because I also write and maintain a suite of plug-ins for our platform, I was running by debugging the Eclipse instance from an Eclipse with all of my plug-ins in...

No, it's still playing up outside of Eclipse debugging. I just deployed everything to a standalone Eclipse (built my plug-ins and updated the set-up to my latest via my update...

Going back to debugging, it works again, but only if I step through the code up until the time we're actually in the job that does `DebugPlugin.getDefault().getLaunchManager().addLaunch(pendingLaunch);` If I don't...

I thought the problem may be that `DebugUITools.launch` is being called outside of the UI thread. See the comment on the method: ``` /** * Saves and builds the workspace...

It's one of those whose behavior is altered too much by debugging/observing it, so very frustrating to solve :)