GWT plugin 3.8.0 v201410302155 r43 with GWT 2.4.0 SDK : superDevMode argument auto injected in Google Run Target + warning missing gwt-codeserver.jar ? under GWT preferences

[GoogleCodeExporter]

Found in GWT Release 2.4.0:

Encountered on OS / Browser (Win7, IE9, FF10):

Detailed description (please be as specific as possible):
Update on GWT plugin changes my GWT preference and option in GWT Run target 
failing in GWT 2.4.0 SDK as -superDevMode arg not supported.

Shortest code snippet which demonstrates issue (please indicate where
actual result differs from expected result):

Workaround if you have one:
adding gwt-codeserver.jar to 2.4.0 sdk remove the warning but not sure as 
linked to superdevmode not available in 2.4.0

Original issue reported on code.google.com by [email protected] on 6 Nov 2014 at 3:59

[GoogleCodeExporter]

Issue 8986 has been merged into this issue.

Original comment by t.broyer on 10 Nov 2014 at 9:55

[GoogleCodeExporter]

I have same problem...
What is the solution?

Original comment by [email protected] on 14 Nov 2014 at 1:44

[GoogleCodeExporter]

Same problem here... hoping for a solution

Original comment by [email protected] on 20 Nov 2014 at 5:07

[GoogleCodeExporter]

the latest version of the GWT Plugin under Eclipse remove the issue since 
3.8.0..r44 the noSuperDevMode option appears and the superDevMode is not 
automatically addded.

The solution (more a workaround) is to add the codeserver.jar temporary under 
the GWT 2.4.0 SDK folder to add it under the Eclipse > Window > Preferences > 
Google > Web Toolkit (Add...)

Once your GWT project have the GWT Container added to your classpath, you 
should be fine and you can remove the codeserver.jar . Still remain the warn & 
error under Eclipse > Window > Preferences > Google > Web Toolkit but it works 
fine.

Hope it will help.

Beside I was aware of too long classpath resolution on GWT SDK 2.7 but I cannot 
the find any references in the Release notes, any help is helpful. Our project 
get so many jars dependencies throught maven that the classpath that it is 
getting a real issue (BTW no support of Bundle ClassPath by GWT so far...one 
day maybe)  

Original comment by [email protected] on 3 Dec 2014 at 2:33

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

To stop the -superDevMode flag from getting auto injected I made the Eclipse 
Run Configuration file read-only.

Example path: 
<YOUR_WORKSPACE>\.metadata\.plugins\org.eclipse.debug.core\.launches\<YOUR_RUN_C
ONFIG_NAME>.launch

Then whenever you look at the Dev Mode Run Configuration in Eclipse it will 
still show the -superDevMode flag, but when you click the Close button it now 
asks you if you want to save and you can press No.

On a somewhat related note: if you decide to hand edit that .launch file in a 
text editor Eclipse won't notice your changes. Just restart Eclipse though, and 
it'll see your changes.

Original comment by [email protected] on 4 Feb 2015 at 9:13

[GoogleCodeExporter]

Thanks for this idea... little hack... I guess we have to move to 2.7 

Do you have any feedback on GWT classpath too long issue ?

Original comment by [email protected] on 9 Feb 2015 at 10:28

[GoogleCodeExporter]

(luckily) I haven't comes across the classpath too long issue

Original comment by [email protected] on 10 Feb 2015 at 7:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Here's a Google Groups post on a similar (same?) issue saying they've fixed 
this issue, but haven't yet rolled a release including the fix:

https://groups.google.com/forum/#!topic/google-plugin-eclipse/E7tG9tvaY4M

Original comment by [email protected] on 10 Feb 2015 at 7:08

[GoogleCodeExporter]

And here's someone else that ran into the same issue:

http://stackoverflow.com/q/28026198/152061

Original comment by [email protected] on 10 Feb 2015 at 7:09