I'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it.
Reading the docs on Debugging, they do kind of explain this - but there are places where they reference what appears to be the original way of running Super Dev Mode using bookmarklets, As above, those of us using these are not finding they work. Also, for us, we don't run the embedded Jetty so need to run standalone server. Falling back to our old Dev Mode launch script, it does try to launch Super Dev Mode but aborts with an error: Super Dev Mode starting up > workDir: C:\Temp\gwt-codeserver-8197845274977519094.tmp > Loading Java files in GwtApiTas. > * Ignored 308 units with compilation errors in first pass.* > Compile with -strict or with -logLevel set to TRACE or DEBUG to see all > errors. > Module setup completed in 4878 ms > Loading Java files in VtWebUi. > * Ignored 310 units with compilation errors in first pass.* > Compile with -strict or with -logLevel set to TRACE or DEBUG to see all > errors. > Resolving com.ascert.tas.gwtapi.client.driverlib.DriverlibService > Found type 'com.ascert.tas.gwtapi.client.driverlib.DriverlibService' > Resolving method getDriverDescriptor > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method getPackagedEnvironments > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method getRepositories > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckReturn > Resolving method refreshRepository > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method deletePackages > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method downloadPackages > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method pinPackage > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Resolving method unpinPackages > [WARN] Ignoring unresolvable annotation type > com.ascert.tas.gwtapi.c > lient.security.VtasSecurityCheckMethod > Finding entry point classes > * [ERROR] Hint: Check the inheritance chain from your module; it may > not be* > *inheriting a required module or a module may not be adding its source > path entri* > *es properly* > We don't have 600 sources with errors, since it clean compiles and runs fine. So I'm guessing it has something to do with source paths, given the number of modules skipped with errors. But at this stage I'm still lost. Overall this was not a well documented or explained transition! I am really not surprised the average users are battling with it -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/7141631c-513b-4a58-8d0f-39098bff646d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
