Reduce the number of GWT permutations in maven build

I am refactoring a GWT project to build beyond eclipse using maven and the GWT plugin. When I create the application in eclipse, it finds my one module and compiles 5 substitutions. When I build the same with the gwt plugin, it should compile 75, which requires age. The increase in the number of local workers did not help with speed even

I do not limit user agents or locales in the assembly, so why does the eclipse assembly compute so many fewer permutations, and how can I get maven build to do the same?

Maven compilation uses the following options

com.google.gwt.dev.Compiler -gen / project / target / .generated -logLevel INFO-style OBF -war / project / target / war -localWorkers 1 mymodule

+8
compilation permutation gwt
source share
2 answers

For me, by default you need to create for 6 browsers. When I point to Safari, it only builds one permutation. Also, if you have any localization of / i 18n for languages, you will multiply these permutations with those. This happened to me when I tried to set my default language to β€œen”, so I just didn't worry about it and left it as β€œdefault”.

MyApplication.gwt.xml

<!-- only build for Chrome --> <set-property name="user.agent" value="safari" /> 
+9
source share

Take a look at the GWT-Maven documentation plugin: here (optimizationLevel) and here (draftCompile)

or read here about generating a specific engine only.

+6
source share

All Articles