Current state of one .js file per module

Hi.

I created an issue several months ago - https://code.google.com/p/google-web-toolkit/issues/detail?id=8581 to split up generated .js.

The answer was that a .js file, with its corresponding source map, would be generated per module.

I'm analyzing now (with GWT 2.7.0) the output, and I still have 1 single monolithic, .js file and a single source map.

Has this subject been aborted, postponed, or just not enabled by default?

My project is big. It would be great if the files were split per module, as commented in the issue.

 

I'd love to improve this, and reduce the timings on it.

Specially between runs - sometimes small incompatible debug changes in server side forces a restart - and a new compilation.

In this case, the reload button doesn't help, as the JVM is inconsistent anyway.

Just for the record, here's the compilation log for the project (the real module was changed to package.Project).

 

GET /recompile/project

Job package.Project_1_0

starting job: package.Project_1_0

binding: user.agent=safari

Compiling module package.Project

Unification traversed 99049 fields and methods and 8257 types. 8223 are considered part of the current module and 8223 had all of their fields and methods traversed.

Compiling 1 permutation

Compiling permutation 0...

Linking per-type JS with 8207 new types.

prelink JS size = 21670288

prelink sourcemap = 21670288 bytes and 461483 lines

postlink JS size = 21503531

postlink sourcemap = 21503531 bytes and 458742 lines

Source Maps Enabled

Compile of permutations succeeded

Compilation succeeded -- 87,370s

Linking into /tmp/gwt-codeserver-6688054585701610251.tmp/package.Project/compile-2/war/project; Writing extras to /tmp/gwt-codeserver-6688054585701610251.tmp/package.Project/compile-2/extras/project

Link succeeded

Linking succeeded -- 2,417s

90,304s total -- Compile completed