>
> 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
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
SGTM.
On Wed, Oct 29, 2014 at 12:58 PM, 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> 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. Th
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
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.
-
