Re: Closure compiler removal ?

Another question related to that. How can be integrated closure optimization in the build after that?

On Fri, 10 Jun 2016 at 16:32 Hristo Stoyanov <hr.stoyanov@gmail.com> wrote:

According to this:
https://gwt-review.googlesource.com/#/c/15110/

The -XenableClosudeCompiler option will be removed from GWT 2.8. This impacts Cradle And Maven plugins. I also have 2 question:
1. Is specifying -optimte 9 good enough to be the only one left?
2. The reason for the removal states that it never worked with source maps, but source maps are only useful during development, when noone uses optimization?

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.