Certain gwtar files seem to be way too large in GWT 2.7

[Jens]

The increased *.gwtar file size results in a gwt-user.jar which is 80MB in size, up from 29MB. This really hurts when using the SNAPSHOT build of GWT through Maven/Gradle. I guess there is something wrong in the build script and stuff gets repackaged multiple times.


GWT 2.7.1:
 
jens-mba:gwt-user-2.7.0-beta1 Jens$ ls -laRh | grep .gwtar 
 
-rw-r--r--@ 1 Jens staff 50M 18 Okt 09:16 Activity.gwtar 
-rw-r--r--@ 1 Jens staff 5,6M 18 Okt 09:16 Core.gwtar 
-rw-r--r--@ 1 Jens staff 56M 18 Okt 09:16 Debug.gwtar 
-rw-r--r--@ 1 Jens staff 172K 18 Okt 09:16 JSON.gwtar 
-rw-r--r--@ 1 Jens staff 57M 18 Okt 09:16 Logging.gwtar 
-rw-r--r--@ 1 Jens staff 6,0M 18 Okt 09:16 Place.gwtar 
-rw-r--r--@ 1 Jens staff 42K 18 Okt 09:16 RegExp.gwtar 
-rw-r--r--@ 1 Jens staff 57M 18 Okt 09:16 User.gwtar 
-rw-r--r--@ 1 Jens staff 480K 18 Okt 09:16 XML.gwtar 
-rw-r--r--@ 1 Jens staff 794K 18 Okt 09:16 AutoBean.gwtar 
-rw-r--r--@ 1 Jens staff 195K 18 Okt 09:16 Event.gwtar 
-rw-r--r--@ 1 Jens staff 58M 18 Okt 09:16 RequestFactory.gwtar
 
 
 
GWT 2.6.1:
 
jens-mba:gwt-user-2.6.1 Jens$ ls -laRh | grep .gwtar 
 
-rw-r--r--@ 1 Jens staff 78K 7 Mai 13:59 Activity.gwtar 
-rw-r--r--@ 1 Jens staff 6,0M 7 Mai 13:59 Core.gwtar 
-rw-r--r--@ 1 Jens staff 21K 7 Mai 13:59 Debug.gwtar 
-rw-r--r--@ 1 Jens staff 167K 7 Mai 13:59 JSON.gwtar 
-rw-r--r--@ 1 Jens staff 299K 7 Mai 13:59 Logging.gwtar 
-rw-r--r--@ 1 Jens staff 140K 7 Mai 13:59 Place.gwtar 
-rw-r--r--@ 1 Jens staff 39K 7 Mai 13:59 RegExp.gwtar 
-rw-r--r--@ 1 Jens staff 551K 7 Mai 13:59 RPC.gwtar 
-rw-r--r--@ 1 Jens staff 51M 7 Mai 13:59 User.gwtar 
-rw-r--r--@ 1 Jens staff 443K 7 Mai 13:59 XML.gwtar 
-rw-r--r--@ 1 Jens staff 753K 7 Mai 13:59 AutoBean.gwtar 
-rw-r--r--@ 1 Jens staff 189K 7 Mai 13:59 Event.gwtar 
-rw-r--r--@ 1 Jens staff 1,4M 7 Mai 13:59 RequestFactory.gwtar


-- J.

[Jens]

I think the problem is that GWT module dependencies have changed due to library compilation constraints (no circular module deps) and the build file has not been updated to reflect that.

Would it make sense to have one *.gwtar file per GWT module that is not marked as type=fieldset ?

-- J.

[Daniel Kurka]

Jens and I talked offline.

Since gwttars are only relevant for the prod compile and do not impact SDM compile times, we don't really need them anymore. They are not used within Google and we do not want to maintain them going foward.

So I suggest we deprecate them with GWT 2.7 and disable them and remote them going forward.

-Daniel

--
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 google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad05e8d4-6bf8-4223-bd8a-f24939791ee0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Google Germany GmbH

Dienerstr. 12
80331 München

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

[Goktug Gokdogan]

SGTM.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip7WPpMssr5PvM_tGk4dERWZFXUDRvdwmWqKES%2B%3DBSp2Q%40mail.gmail.com.

[Thomas Broyer]

On Wednesday, October 29, 2014 8:58:07 PM UTC+1, Daniel Kurka wrote:

Jens and I talked offline.

Since gwttars are only relevant for the prod compile and do not impact SDM compile times, we don't really need them anymore. They are not used within Google and we do not want to maintain them going foward.

So I suggest we deprecate them with GWT 2.7 and disable them and remote them going forward.

I think I already proposed it some time ago (after someone told me that Google doesn't actually use them) and got some feedback that they make their build faster.

A quick search in the groups gave me https://groups.google.com/d/msg/google-web-toolkit/O8HaPzExxhc/X16AnKZI2JAJ, but nothing more.

[Jens]

I think I already proposed it some time ago (after someone told me that Google doesn't actually use them) and got some feedback that they make their build faster.

A quick search in the groups gave me https://groups.google.com/d/msg/google-web-toolkit/O8HaPzExxhc/X16AnKZI2JAJ, but nothing more.

Does anybody know how much compile time is actually saved by using gwtar files? I have no idea and generally I don't care if a production compile takes 10 or 15 minutes.

It is just a bit unfortunate that the build file needs to be in sync with GWT module inheritance but maybe it is possible to write a gwtar tool that always does the right thing based on the given module inheritance (naive thoughts: generate a gwtar per graph clique or start with a defined module and do a breadth first traversal to generate one gwtar per module). Then users who want to use that feature could run the tool, but the GWT build would not do so by default. Or GWT does continue to generate them but packages the result in a different jar that is an optional dependency.

At the end I am only interested in having small SDK download sizes as I use SNAPSHOT builds in private projects. So I am also fine with just getting rid of gwtar files.

-- J.