Have GWT 2.7.0 SuperDevMode reuse old compile-n files from last run

[salek....@googlemail.com]

Hello,

I'm using GWT 2.7.0 SuperDevMode and start the codeserver from Eclipse Luna SR2 under Win 8.1, but as plain Java application without using the Eclipse plugin.

My log starts with these lines on startup all the time:

Turning off precompile in incremental mode.

Super Dev Mode starting up

   workDir: C:\Users\myuser\workspace\myproj\codeserver

   Public resources found in...

   Translatable source found in...

log4j:WARN No appenders could be found for logger (org.eclipse.jetty.util.log).

log4j:WARN Please initialize the log4j system properly.

   Loading Java files in mymodule.

   Persistent unit cache dir set to: C:\Users\myuser\workspace\myproj\codeserver\mymodule\compile-1\gwt-unitCache

   Looking for previously cached Compilation Units in C:\Users\myuser\workspace\myproj\codeserver\mymodule\compile-1\gwt-unitCache

   Found 0 cached/archived units.  Used 0 / 4872 units from cache.

   Compiling...

      0% complete (ETR: ?)

      10% complete (ETR: 350 seconds)

      20% complete (ETR: 217 seconds)

      30% complete (ETR: 231 seconds)

      40% complete (ETR: 183 seconds)

      50% complete (ETR: 143 seconds)

      60% complete (ETR: 105 seconds)

      70% complete (ETR: 71 seconds)

      80% complete (ETR: 44 seconds)

      90% complete (ETR: 21 seconds)

      100% complete (ETR: 0 seconds)

      Compilation completed in 219,33 seconds

   Added 4872 units to cache since last cleanup.

Is it somehow possible to have the codeserver use the old data from compile-1, compile-2, compile-3... instead of starting with a full compile on startup every time?

It seems there is no need for this (the incremental compiling after a change works), so I think it should be possible.

Could this be related to the way Eclipse ends the codeserver (terminates it), so that it can't "clean up" for the next start?

My startup parameters are as follows:

-src src -workDir ${workspace_loc:myproj}/codeserver -port 1234 mymodule -logLevel TRACE -war C:\Users\myuser\workspace\myproj\war -incremental -precompile -workDir C:\Users\myuser\workspace\myproj\codeserver

Thank you & Best regards

Salek

[Brandon Donnelson]

Eclipse uses the entrypoint, so this wouldn't have anything to do with Eclipse. 

[Jens]

Not sure if it did make into GWT 2.7 but at least 2.8-SNAPSHOT uses some caches when you restart SDM. It still takes a bit but its a lot faster than with previous versions of SDM.

-- J.

[salek....@googlemail.com]

Answering my own question:
This seems to work if you start SDM from the Eclipse Plugin (=as Web Application) and not as normal Java Application.
Also, you do not need the bookmarklets then, a recompile is triggered on browser refresh (tested FF26, GC42, IE11).

[Thomas Broyer]

You shouldn't need the bookmarklets either when launching CodeServer "as a Java Application", provided you pass the -launcherDir argument (the -war argument is a synonym) pointing to the folder your webserver looks at for web resources.