Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

Sure, these are the job configurations. Let me know if you need anything
else.



On Wed, Jun 17, 2020 at 9:36 AM Colin Alworth 
wrote:

> Can you share the jenkins configurations as they exist today to ease the
> migration process? They don't seem to be checked in to the build glue or
> any other repository I noticed on the gwt.googlesource.com repo.
>
> --
>   Colin Alworth
>   co...@colinalworth.com
>
>
>
> On Wed, Jun 17, 2020, at 10:29 AM, 'Roberto Lublinerman' via GWT
> Contributors wrote:
>
> The Jenkins server is online, however due to new security related policies
> on the compute engine vms run by our teams, we cannot give public access to
> the Jenkins instance.
>
> The CI build is running as scheduled. The presubmit is broken, as far as I
> can tell it was broken long ago by a Jenkins update. It seems that our go
> presubmit code needs to be updated on how it does the presubmit request to
> Jenkins, I think it just needs to be changed from http get to http post.
>
> Given the low number of contributions I do not mind triggering presubmit
> manually, so just ping me. But moving forward, the CI server needs to be
> moved out of our internal infrastructure. If you want to have a look on
> why the presubmit trigger (
> https://gwt.googlesource.com/buildglue/+/refs/heads/master/jenkins/jenkins.go)
> is failing you could probably replicate it locally and if anybody
> contributes a fix I'll apply it to our server. I currently do not have much
> bandwidth to devote to any of this.
>
>
> On Wed, Jun 17, 2020 at 12:59 AM Jens  wrote:
>
> Any news here?
>
> The Leeroy Jenkins spam is really annoying in code reviews.
>
> -- J.
>
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/4d9695b1-bf52-4792-a0c5-c4cb413487abo%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/4d9695b1-bf52-4792-a0c5-c4cb413487abo%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmMbRX6avp6Ca%2BNCye0kH5R8%3DSS%2B9%2Bv%2B6c3qAkwGOLdQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmMbRX6avp6Ca%2BNCye0kH5R8%3DSS%2B9%2Bv%2B6c3qAkwGOLdQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/6bbd26e9-a3a8-4140-b69f-d3897a534815%40www.fastmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/6bbd26e9-a3a8-4140-b69f-d3897a534815%40www.fastmail.com?utm_medium=email_source=footer>
> .
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gn_1xEOWLZwRNLrrKt5e%2B6tMyqx54XdkzMY2RbXR3HK0A%40mail.gmail.com.
<>

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

The Jenkins server is online, however due to new security related policies
on the compute engine vms run by our teams, we cannot give public access to
the Jenkins instance.

The CI build is running as scheduled. The presubmit is broken, as far as I
can tell it was broken long ago by a Jenkins update. It seems that our go
presubmit code needs to be updated on how it does the presubmit request to
Jenkins, I think it just needs to be changed from http get to http post.

Given the low number of contributions I do not mind triggering presubmit
manually, so just ping me. But moving forward, the CI server needs to be
moved out of our internal infrastructure. If you want to have a look on
why the presubmit trigger (
https://gwt.googlesource.com/buildglue/+/refs/heads/master/jenkins/jenkins.go)
is failing you could probably replicate it locally and if anybody
contributes a fix I'll apply it to our server. I currently do not have much
bandwidth to devote to any of this.


On Wed, Jun 17, 2020 at 12:59 AM Jens  wrote:

> Any news here?
>
> The Leeroy Jenkins spam is really annoying in code reviews.
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/4d9695b1-bf52-4792-a0c5-c4cb413487abo%40googlegroups.com
> 
> .
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmMbRX6avp6Ca%2BNCye0kH5R8%3DSS%2B9%2Bv%2B6c3qAkwGOLdQ%40mail.gmail.com.

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

I'll have a look at the Jenkins configuration tomorrow.

On Sun, May 3, 2020 at 6:37 AM Colin Alworth  wrote:

> The build is failing again, two days in a row, and since this is shortly
> after the jsinterop-annotation change, there is concern that this failure
> is a result of that change. Can a googler look into this, or grant us the
> ability to do so?
>
> Thanks,
> Colin
>
> On Monday, July 22, 2019 at 12:48:34 PM UTC-5, Roberto Lublinerman wrote:
>>
>> The issue is still not completely resolved and build.gwtproject.org is
>> still unreachable. However continuous builds and presubmits should be
>> working now.
>>
>> On Sun, Jul 7, 2019 at 4:39 AM Roberto Lublinerman 
>> wrote:
>>
>>> I am currently on vacation. The issue is that because of security
>>> concerns new policies are in place regarding use of compute engine by
>>> Google teams. Http and https have been blocked by an enforcer bot. I will
>>> sort this out when I get back. There might be a need to transition out of
>>> this configuration.
>>>
>>> So for now build.gwtproject.org will remain inaccessible, the server
>>> though it's still running, pulls the changes, does the fast check but is
>>> unable to start the presubmit since it does so through an http post on
>>> build.gwtproject.org.
>>>
>>> I'll let you know how it goes.
>>>
>>>
>>>
>>> On Sat, Jul 6, 2019, 12:58 Jens  wrote:
>>>
>>>>
>>>> fixed
>>>>>
>>>>
>>>> Hmm, build.gwtproject.org still isn't accessible for me and Jenkins
>>>> still does an endless check as soon as +1 or +2 is given.
>>>>
>>>> -- J.
>>>>
>>>> --
>>>> 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-contributors+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc58ea21-f502-4a85-9571-81b43f564630%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc58ea21-f502-4a85-9571-81b43f564630%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/c520c1f1-2b2f-4b7e-95f7-b3fba534dfa0%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/c520c1f1-2b2f-4b7e-95f7-b3fba534dfa0%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gn8UvAB4QD%2BAiTRDq9d93CYXLwAbwp2O7%3DrwpFGE%2BfY7A%40mail.gmail.com.

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

The issue is still not completely resolved and build.gwtproject.org is
still unreachable. However continuous builds and presubmits should be
working now.

On Sun, Jul 7, 2019 at 4:39 AM Roberto Lublinerman 
wrote:

> I am currently on vacation. The issue is that because of security concerns
> new policies are in place regarding use of compute engine by Google teams.
> Http and https have been blocked by an enforcer bot. I will sort this out
> when I get back. There might be a need to transition out of this
> configuration.
>
> So for now build.gwtproject.org will remain inaccessible, the server
> though it's still running, pulls the changes, does the fast check but is
> unable to start the presubmit since it does so through an http post on
> build.gwtproject.org.
>
> I'll let you know how it goes.
>
>
>
> On Sat, Jul 6, 2019, 12:58 Jens  wrote:
>
>>
>> fixed
>>>
>>
>> Hmm, build.gwtproject.org still isn't accessible for me and Jenkins
>> still does an endless check as soon as +1 or +2 is given.
>>
>> -- J.
>>
>> --
>> 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-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc58ea21-f502-4a85-9571-81b43f564630%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc58ea21-f502-4a85-9571-81b43f564630%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkX1%3DxdBB_sV1UzXnq%2B23xsQVVkvM2uf8JHbCs3Wa9FGQ%40mail.gmail.com.

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

I am currently on vacation. The issue is that because of security concerns
new policies are in place regarding use of compute engine by Google teams.
Http and https have been blocked by an enforcer bot. I will sort this out
when I get back. There might be a need to transition out of this
configuration.

So for now build.gwtproject.org will remain inaccessible, the server though
it's still running, pulls the changes, does the fast check but is unable to
start the presubmit since it does so through an http post on
build.gwtproject.org.

I'll let you know how it goes.



On Sat, Jul 6, 2019, 12:58 Jens  wrote:

>
> fixed
>>
>
> Hmm, build.gwtproject.org still isn't accessible for me and Jenkins still
> does an endless check as soon as +1 or +2 is given.
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fc58ea21-f502-4a85-9571-81b43f564630%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnBfWiW3KUqMXohJ-X%2BNKaBTJZXGceOQRFREYar1a3sVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

It seems that we are running the build server in a way that a new
enforcement mechanism disables http https serving. I'll follow up on the
issue when I return.

On Sun, Jun 30, 2019 at 1:30 PM Roberto Lublinerman 
wrote:

> fixed
>
> On Sun, Jun 30, 2019 at 1:20 PM Roberto Lublinerman 
> wrote:
>
>> It seems that there was some automatic configuration change that added a
>> few firewall rules. I am looking into this but I will be out for a couple
>> of weeks and I don't know if I'll be able to fix that before I return.
>>
>> On Sat, Jun 29, 2019 at 12:42 PM Jens  wrote:
>>
>>> Can anybody with the appropriate permissions mark
>>> https://gwt-review.googlesource.com/c/gwt/+/21680 as verified so it can
>>> be merged and possibly figure out why Jenkins does an endless fast style
>>> check?
>>>
>>> Also http://build.gwtproject.org isn't reachable for me. Wondering if
>>> there is really an issue with the server or if some network route is broken.
>>>
>>> -- J.
>>>
>>> --
>>> 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-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/75d073bf-8b32-481b-9435-dd86ea29d2eb%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/75d073bf-8b32-481b-9435-dd86ea29d2eb%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmLOSYRxKMZ6GpZJXvxnPp_TzOG29sTgOWKiYHBaZ_Q5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] CI / Jenkins configuration issue

['Roberto Lublinerman' via GWT Contributors]

It seems that there was some automatic configuration change that added a
few firewall rules. I am looking into this but I will be out for a couple
of weeks and I don't know if I'll be able to fix that before I return.

On Sat, Jun 29, 2019 at 12:42 PM Jens  wrote:

> Can anybody with the appropriate permissions mark
> https://gwt-review.googlesource.com/c/gwt/+/21680 as verified so it can
> be merged and possibly figure out why Jenkins does an endless fast style
> check?
>
> Also http://build.gwtproject.org isn't reachable for me. Wondering if
> there is really an issue with the server or if some network route is broken.
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/75d073bf-8b32-481b-9435-dd86ea29d2eb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3D5VTH%3DVLq%2B_YmG3yP%2B%3DsAES3k7%3DKxQiOdUMfsA0qiqVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Fwd: Happy to announce general access for J2CL!

['Roberto Lublinerman' via GWT Contributors]

To save you some pain, you should probably use the WSL (Windows Subsystem
for Linux). You can track the progress for and contribute to making it work
natively in https://github.com/google/j2cl/issues/9.

On Wed, Nov 21, 2018 at 4:32 PM Jason Washo  wrote:

> Awesome! I'm starting the process now. Windows user, and looking forward
> to it!
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/433b82b7-0265-41a3-ad63-54ea55dda5f1%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkhQfn4UycLAXph4Dy6xbAJ%3DZ_qY8PomAYfhY%3Da4kmLEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Wrong deobfuscated stack traces

['Roberto Lublinerman' via GWT Contributors]

Looking at this traces it seems to me that the file/line is consistent but
the member is completely off. That suggests that the wrong symbol map is
being used.

On Mon, Jul 30, 2018 at 4:40 AM Jens  wrote:

> In production we sometimes get exceptions and we log them using
> StackTraceDeobfuscator class on the server (either symbol maps or source
> maps, depending on browser). However these stack traces are often broken
> when comparing the member with the file it should live in.
>
> Some examples:
>
> at Unknown.removeChild(Unknown@-1)
> at
> com.google.gwt.dom.client.Node.$removeChild(com/google/common/base/Joiner.java:198)
> at
> com.google.gwt.user.client.ui.SimplePanel.$remove(com/google/common/collect/super/com/google/common/collect/ImmutableList.java:41)
> at
> com.google.gwt.user.client.ui.SimplePanel.remove(com/google/common/collect/super/com/google/common/collect/ImmutableMap.java:239)
> at com.google.gwt.user.client.ui.SimplePanel$1.remove(SimplePanel.java:93)
> at
> com.google.gwt.user.client.ui.Panel.$clear(com/google/gwt/user/client/ui/Panel.java:75)
>
>
> at
> java.lang.Throwable.Throwable(com/google/gwt/emul/java/util/AbstractCollection.java:68)
> at
> java.lang.RuntimeException.RuntimeException(com/google/gwt/emul/java/util/AbstractList.java:208)
> at
> com.google.web.bindery.event.shared.UmbrellaException.UmbrellaException(com/google/common/collect/super/com/google/common/collect/ForwardingImmutableMap.java:108)
> at
> com.google.web.bindery.event.shared.SimpleEventBus.$doFire(com/google/common/collect/super/com/google/common/collect/ImmutableList.java:281)
> at
> com.google.gwt.place.shared.PlaceController.$goTo(com/google/gwt/emul/java/util/AbstractMap.java:167)
>
>
> at
> com.google.web.bindery.event.shared.UmbrellaException.UmbrellaException(UmbrellaException.java:656)
> at
> com.google.gwt.event.shared.UmbrellaException.UmbrellaException(com/google/gwt/http/client/Request.java:247)
> at
> com.google.gwt.event.shared.HandlerManager.$fireEvent(HandlerManager.java:638)
>
>
> Any idea how this could happen and where to look at, or is this kind of
> expected with current compiler?
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2303e9b2-bf7c-4f67-9bf4-7b3fe5b83145%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnv8tdYyCQf38_MoSSYgVT5y0L245%2BH5iuFTcWBmm94SQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: IntelliJ IDEA project config

['Roberto Lublinerman' via GWT Contributors]

You can also set it up from the gradle build script here:
https://gwt-review.googlesource.com/c/gwt/+/7984. It is quite outdated but
I think with minimal work it might be brought up to date. I have used it in
the past with success.

On Wed, Apr 25, 2018 at 1:28 AM Jens  wrote:

> It is pretty annoying to setup GWT correctly in IntelliJ :( Quite some
> time ago I had one working, but in the mean time a bit has changed in terms
> of emulation packages and libraries.
>
> You can use the old state as a starting point:
> https://gwt-review.googlesource.com/c/gwt/+/12380 (see Readme before
> opening the project)
>
> One of the major annoyances in IntelliJ is figuring out a way to handle
> all these super source excludes in source folders correctly.
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/24ae5ed4-95ed-427c-963e-d52e5d8f681e%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk3FqtisTCf3b3oKmZEsQCLROBQJy-7zNJb8%3D%3DNo9X83w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java10 support

['Roberto Lublinerman' via GWT Contributors]

On Mon, Apr 9, 2018 at 11:19 PM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:

> I'm stuck with a few issues in JDT compiler those make not possible to
> launch "super sourced" tests at source level >= 9.
> So, I have to first make patches for JDT and create custom JDT build
> before proceeding with patch for JEP286.
>

Hmm. One option is to wait till JDT stabilizes. The required patches are
probably going to be part 4.8M7 (or whatever follows the M6). For testing
purposes you could use
http://download.eclipse.org/eclipse/downloads/drops4/I20180409-2000/ or the
latest or more stable integration build which contains the patches but you
are probably using this one judging from the commit you are referencing at
the end.

Just for information.
> The first issue with JDT is about how GwtIncompatible annotaion handled by
> the GWT compiler.
> JDT AST TypeDeclaration may contains empty arrays of methods and fields
> after applying GwtIncompatible.
> But JDT assumes that for type without methods and fields the corresponding
> members are equal to `null` instead of empty arrays.
> E.g.: TypeDeclaration.java#L730
> 
> The line above throws AIOOBE for type wich methods had been removed due to
> GwtIncompatible.
> On other side, this issue may be fixed on GWT side, I think.
>

Yes, this can be fixed in GwtIncompatiblePreprocessor. Previously JDT used
zero length arrays instead of null, but null should be fine if it doesn't
trip any of our assumptions.


> The second issue is a bug with handling Deprecated annotation that was
> introduced in
> https://github.com/eclipse/eclipse.jdt.core/commit/79d5afecf5f237634a5562279fdceca6591b2b58
> .
> This issue leads to AIOOBE when there is an annotation marked as
> Deprecated. I noticed this issue for GwtScriptOnly annotation.
>

Intermediate builds of JDT are normally quite fragile, I wouldn't be
surprised if this is the case. Just out of curiosity what is it stack trace
for this failure? Might it have been triggered by a changed assumption in
JDT?


> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/37d9249d-0a6a-4403-b07d-e3cb09492bc5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmP81A3rgkBOGm2sLrq5EEd5MZCornt3upEfSdaGPg7HQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java10 support

['Roberto Lublinerman' via GWT Contributors]

On Thu, Apr 5, 2018 at 10:59 PM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:

> Ok. I'll prepare and upload the patch.
>
> Thanks for pointing out the solution's direction.
>

Np. Thanks for contributing to the compiler proper :).

I was giving another look at the code and the safest place to fix (if the
problem is what I think it is) is in ReferenceMapper.createType. The name
computed there assumes that is not a local class (not anonymous nor local)
because locals and anonymous would be seen in the source before their
usages and be registered as source types (not external).

I am not sure if the binding we get there from the variable is a
LocalTypeBinding, but if it is, then you can extract the name computation
from GwtAstBulider.createTypes and use it in both situations. If it is not
a LocalTypeBinding you can actually just see if it is isAnonymousType() and
and use a similar logic.

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkFt8qSM_Asdg%2BrPWPMccivMGsZOsSN91zfF%3Dkyx1Mu-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java10 support

['Roberto Lublinerman' via GWT Contributors]

On Thu, Apr 5, 2018 at 2:07 AM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:

>
> Yes, all i had to do to make non-denotable type to work, is to replace
> `$Local$` type with anonymous synthetic class name `Outer$1` when creating
> JClassType for JLocal.
>
>
Ok.  So you changed GwtAstBuilder and to get the actual type from the
typebinding in GwtAstBuilder.createLocal? Could you upload the patch to gwt
so I can comment there? :) It might just be the case that because the
variable declaration happens before the Anonymous inner class s created it
has not been registered in typeMap, and probably this is the only case in
which a variable declaration can have the type of local or anonymous class
that is defined after.

I am guessing that your fix is in GwtAstBuilder. The error shows in
UnifyAst only because the case is not properly handled in GwtAstBuilder. If
not then that is where it should be.

Regarding tests - are you sure that GwtAstBuilderTest is a sutable place
> for these tests? I noticed that Java9 tests were placed into the new
> class Java9AstTest.
>

You can write it in either GwtAstBuilderTest or introduce a Java10AstTest.
In any case you would want to add a programmatic assertion that the type of
the variable is the anonymous class (something in the spirit of
GwtAstBuilder.testIntersectionBound).

And also add integration tests in Java8Test (see how this is done because
Java8Test is super sourced), you coul introduce Java10Test using Java8Test
as a model.

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnd318LyGb%3DARzz_Lr0Dz%2B0%3Di8xVpa8nTW_%3Ds8UQvEwaw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java10 support

['Roberto Lublinerman' via GWT Contributors]

On Wed, Apr 4, 2018 at 12:36 AM Alexander Leshkin <
alexander.lesh...@gmail.com> wrote:

But for non-denotable types GWT compiler breaks with assertion. E.g. it
> breaks for anonymous local class:
> var tuple = new Object(){ int first, second; };
>
> It's because type binding for this declaration looks like:
> $Local$ tuple = new Outer$1();
>
> So,it looks like some changes in GWT compiler still have to be made to
> support JEP 286.
>

In any  case, I don't expect the compiler changes to be significant. There
are no new abstraction to be introduced nor structural changes. Could you
start adding tests to GwtAstBuilderTest for these cases, even if they have
to be disabled or commented out.

BTW, which assertion is failing, is it one in JProgram.createLocal?

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk2y7mx-5bFJ36ifBFoJopUeiM498zmp7_XhY0e3FODcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Code reviews on compiler patches

['Roberto Lublinerman' via GWT Contributors]

Anybody up for reviewing https://gwt-review.googlesource.com/c/gwt/+/20580?

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DSjUi8NqPzc07HnUDgX6n%2Bqy3Hgj11X7LeawFieaTAUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Gerrit Changes and Merging them into master

['Roberto Lublinerman' via GWT Contributors]

> There are also Java9 depeding issue which will not be reviewed for example.
>>
>
> Yeah I agree, Java9 support, including new API emulations, should find its
> way into GWT sooner than later. GWT usually has to wait for a good Eclipse
> JDT release as GWT uses it to parse and compile GWT sources. There have
> been some updates recently, but I don't know if anyone at Google is
> actively working on updating the GWT compiler to support new Java 9 syntax
> (e.g. private methods in interfaces).
>
>
FYI, the new language features introduced in Java 9 (private interface
methods and a small improvement in try with resources) are already
committed to HEAD (
https://gwt.googlesource.com/gwt/+/6407ba9f1e5c02412035689653484c86f9321992
).

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmm5bvtzuSKN%3D9erW84YJQMA%2BOsYcYJ7Fk-N2-Ho5H73A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Super slow compilation in projects with many wildcard generics

['Roberto Lublinerman' via GWT Contributors]

I would wait until an eclipse jdt release is done and upgrade JDT.

On Tue, Sep 26, 2017 at 10:56 AM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> JDT has a bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=521438) that
> make it super slow to compile some project involving wildcards generics.
> Actually, there are many problems with performance and memory consumption
> since Java 8, this has just lived longer bc it was a bit more difficult but
> seem to be a combination of wildcard+inheritance that makes the internal
> type map to explode. RxJava 2 takes >3min to compile caused by this bug so
> it makes impossible to work with.
>
> The bug has been already solved. It needs to be merged and release in JDT
> and later on, it will be nice to be merged in the GWT JDT version as soon
> as possible, anyway as this seems to be a long process I have already
> released a patched version here.
>
> 
> rxjava-gwt-repo
> 
> https://raw.githubusercontent.com/intendia-oss/rxjava-gwt/mvn-repo/
> 
>
>
> The patched commit is this one https://github.com/ibaca/
> eclipse.jdt.core/commit/995495659bddcaf193c0107f8489e698624ceea7
> And applied in GWT here https://github.com/ibaca/gwt/commit/
> 63218f3d695cfc6ec20fea776908b9801952f462
>
> Do I create an issue in github? What do you think it is better, to just
> add the patch (as I have done) over the last version, or to upgrade to last
> JDT?
>
> PD: this will improve a bit compilation times and memory consumption ;).
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/b564a261-a885-
> 4c80-9125-eceb27d739a7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gm%3DZ0z4Kjgc8gX%2Bs_6WyXKmbANebW-Mfz9Xh6FCCZvuKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java 9

['Roberto Lublinerman' via GWT Contributors]

The correct link for the patches are

https://gwt-review.googlesource.com/#/c/19000/
https://gwt-review.googlesource.com/#/c/19020/

On Wed, Jul 26, 2017 at 6:29 PM, Roberto Lublinerman <rlu...@google.com>
wrote:

> I have uploaded two patches for review to allow GWT to run under a Java 9
> vm.
>
> https://gwt-review.googlesource.com/#/c/19000/
> https://gwt-review.googlesource.com/#/c/19001/
>
> The main issue is (as noted by James) that the class loading has been
> revamped and GWT can no longer assume that the class loaders are
> UrlClassLoaders.
>
> The idea is first to be able to run GWT on a Java 9 vm compiling Java 8
> sources.
>
> On Wed, Jun 14, 2017 at 3:01 PM, James Nelson <ja...@wetheinter.net>
> wrote:
>
>>
>>> It is my understanding that we use ASM to load the annotation attributes
>>> from source classes, and then create a Proxy to load member values /
>>> classes / enums off the classpath.  JDT is not involved at all (strange
>>> that it isn't...).
>>>
>>>
>> The most likely reason we aren't using JDT to compile the annotaitons is
>> we are really only using the parser, but not the linker (no code to emit
>> classfiles)
>>
>> --
>> 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-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/google-web-toolkit-contributors/d08d7ad2-4f67-4118-bf81-
>> 2924fedfddf3%40googlegroups.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/d08d7ad2-4f67-4118-bf81-2924fedfddf3%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnO-OFBnzEKyoF1mi3W4Tqn%2BjE_CDTrNpGU2i98yKPjhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Java 9

['Roberto Lublinerman' via GWT Contributors]

I have uploaded two patches for review to allow GWT to run under a Java 9
vm.

https://gwt-review.googlesource.com/#/c/19000/
https://gwt-review.googlesource.com/#/c/19001/

The main issue is (as noted by James) that the class loading has been
revamped and GWT can no longer assume that the class loaders are
UrlClassLoaders.

The idea is first to be able to run GWT on a Java 9 vm compiling Java 8
sources.

On Wed, Jun 14, 2017 at 3:01 PM, James Nelson  wrote:

>
>> It is my understanding that we use ASM to load the annotation attributes
>> from source classes, and then create a Proxy to load member values /
>> classes / enums off the classpath.  JDT is not involved at all (strange
>> that it isn't...).
>>
>>
> The most likely reason we aren't using JDT to compile the annotaitons is
> we are really only using the parser, but not the linker (no code to emit
> classfiles)
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/d08d7ad2-4f67-
> 4118-bf81-2924fedfddf3%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnkVq8Sxs_My6XPUiFC2QAZwE75y-rC-vT_%3DyS6UV4ZWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Fwd: jsinterop: @JsFunction .length always 0

['Roberto Lublinerman' via GWT Contributors]

Not likely to be implemented in the foreseeable future; your best solution
is to create two JavaScript methods (or JSNI)

function asAccessor(f) {
  return function (a) { return f(a); };
}

function asComparator(f) {
  return function (a, b) { return f(a, b); };
}

It would be possible to implement @JsFunction lambdas without a backing
class and that would result in the function having the same number of
parameters as the lambda. But as I said this is unlikely to be implemented
in the foreseeable future as it would require a new Java AST node and thus
changes throughout the code base.

On Tue, Jun 27, 2017 at 2:28 PM, Vassilis Virvilis <vasv...@gmail.com>
wrote:

> Do you want me to report it as issue? If so where?
>
> Is it possible for @JsFunction magic to implement it some day? or it is
> impossible to be implemented with the current design?
>
> Thanks again for all the answers so far.
>
> Vassilis
>
> On Tue, Jun 27, 2017 at 7:40 PM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> You can call it a missing feature. Clearly not a bug, not everything that
>> can be done in JS is available from Java with interop. For these situations
>> you probably want to have some JS stubs.
>>
>> On Tue, Jun 27, 2017 at 1:09 AM, Vassilis Virvilis <vasv...@gmail.com>
>> wrote:
>>
>>> Ok guys this is the last one - I promise.
>>>
>>> Originally posted in gwt-users.
>>>
>>> Does this count as a bug or at least as a missing feature?
>>>
>>> Thanks
>>>
>>> -- Forwarded message --
>>> From: Vassilis Virvilis <vasv...@gmail.com>
>>> Date: Mon, Mar 6, 2017 at 4:08 PM
>>> Subject: jsinterop: @JsFunction .length always 0
>>> To: google-web-tool...@googlegroups.com
>>>
>>>
>>> Hi,
>>>
>>> in D3 the bisect function takes a function that can be a comparator or
>>> an accessor.
>>>
>>> D3 internall figures it out by counting provided function arguments
>>> length via f.length https://developer.mozilla.org/
>>> en/docs/Web/JavaScript/Reference/Global_Objects/Function/length
>>>
>>> Trying to pass a java @JsFunction fails because @JsFunction objects are
>>> lambda with zero arguments that wrap samMethod.apply() call
>>>
>>> Any ideas? Should I file this as a bug?
>>>
>>>
>>> --
>>> Vassilis Virvilis
>>>
>>>
>>>
>>> --
>>> Vassilis Virvilis
>>>
>>> --
>>> 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-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/google-web-toolkit-contributors/CAKbOjEx1_jOohikJ7nBAfps
>>> E%3DJHtnD6M31PibMzjvcjLn7G1fw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAKbOjEx1_jOohikJ7nBAfpsE%3DJHtnD6M31PibMzjvcjLn7G1fw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/google-web-toolkit-contributors/CAC7T7g%3D_JcBzZaNnjBosA
>> mcQ_Bm8Bn9r-_7LfFi%3DDu5r%2BO1h1A%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3D_JcBzZaNnjBosAmcQ_Bm8Bn9r-_7LfFi%3DDu5r%2BO1h1A%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/google-web-toolkit-contributors/CAKbOjEzKqjBGngrz%3DNES1
> bEe24ejg48mHzBw3L9fLP3JC11_%2BA%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAKbOjEzKqjBGngrz%3DNES1bEe24ejg48mHzBw3L9fLP3JC11_%2BA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnJC5tBdXqwr1B4wYTz4UNLppqxpbp4ydZUe7xx8qYCrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Fwd: jsinterop: @JsFunction .length always 0

['Roberto Lublinerman' via GWT Contributors]

You can call it a missing feature. Clearly not a bug, not everything that
can be done in JS is available from Java with interop. For these situations
you probably want to have some JS stubs.

On Tue, Jun 27, 2017 at 1:09 AM, Vassilis Virvilis 
wrote:

> Ok guys this is the last one - I promise.
>
> Originally posted in gwt-users.
>
> Does this count as a bug or at least as a missing feature?
>
> Thanks
>
> -- Forwarded message --
> From: Vassilis Virvilis 
> Date: Mon, Mar 6, 2017 at 4:08 PM
> Subject: jsinterop: @JsFunction .length always 0
> To: google-web-tool...@googlegroups.com
>
>
> Hi,
>
> in D3 the bisect function takes a function that can be a comparator or an
> accessor.
>
> D3 internall figures it out by counting provided function arguments length
> via f.length https://developer.mozilla.org/en/docs/Web/JavaScript/Referen
> ce/Global_Objects/Function/length
>
> Trying to pass a java @JsFunction fails because @JsFunction objects are
> lambda with zero arguments that wrap samMethod.apply() call
>
> Any ideas? Should I file this as a bug?
>
>
> --
> Vassilis Virvilis
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/CAKbOjEx1_jOohikJ7nBAfpsE%
> 3DJHtnD6M31PibMzjvcjLn7G1fw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3D_JcBzZaNnjBosAmcQ_Bm8Bn9r-_7LfFi%3DDu5r%2BO1h1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Fwd: jsinterop woes: Part 2: return Double[]

['Roberto Lublinerman' via GWT Contributors]

>
>
> @Roberto
> Please note that I am not mixing stuff (java and js objects in the same
> array, or different kind of objects in the same array).
>
> D3 is doing the correct thing here. If you pass an array of something,
> let's say T[] you can expect that you will be getting T and T[] out of D3
> functions (can't really remember the specifics). What I am passing are pure
> js objects modeled with jsinterop, and they still count as js, not java. So
> I am expecting to get back what I feed in / declared at the start.
>
>
D3 is a JS api, even if some function says it will return an array of T, it
is a JavaScript array, so there is no (type) guarantee that the array is of
T. So it is an array of things, all of them of type T.

A java T[] has even stronger semantics, if you set an element it will check
that it is the correct type. So the D3 array is like an Object[] that
happens to be filled all with Ts.


> So what do I want: Double[] to be castable to double[] in the GWT js
> context (not in the java context). I don't know if this is possible but it
> is definitely desirable. (The same for String[] and Boolean[]) and a pony
> of course :-)
>
>
Again here Double[] and double[] have very different semantics in Java.

- you can cast Double[] to Object[] but not double[] to Object[]
- you can store nulls in Double[] but not in double[].

They are semantically different. I agree that in some circumstances it
seems convenient to ignore those. But in general GWT follows Java semantics
(with a few exceptions)


> Thanks again.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/CAKbOjExku8sLUm3Ky7B6OF-gx%
> 3DvgvdP_v8nd-Pi0WNeqzyv06g%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkupiRhKbO9CAmnKO9LUSh26veVjnQ0LqAGemeJvFWm9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Fwd: jsinterop woes: Part 2: return Double[]

['Roberto Lublinerman' via GWT Contributors]

On Mon, Jun 26, 2017 at 10:16 AM, Colin Alworth <co...@colinalworth.com>
wrote:

> The example isn't doing instanceof though, it is just making that the
> return type for the method (albeit through the use of generics). Does this
> suggest that we should stop using arrays to refer to raw JS data, or at
> least expect that generics may fail in interesting ways around them (and at
> runtime of all places)?
>

It is the programmers responsibility to make sure JS methods that are
called satisfy the Java contract they declare, same thing as in JSNI. If
you use non native arrays in JsInterop members you should be getting
"unusable-by-js" warnings.

Also I forgot to mention that you can definitely return JS arrays as
Object[] too.

Of course you can do tricks (as people used to in JSNI) if you know the
edges in the semantics. E.g. returning a Date[] if you are sure there will
be no casts. You also have to be aware that when you use generics there
will be casts at the invocation sites.

If you have raw JS array you should model it with either a NativeJsType[]
or an Object[].


> elemental2.Array is full of cases where [] or ... are used as arguments,
> though this includes generic arrays (as opposed to generics _of_ arrays).
> If I understand you correctly, valid Java code that is passed a String[] or
> Double[] (or for example Element[]) may fail in exciting ways if passed one
> of these 'arrays'.
>

varargs is a different animal, JS varargs are always cast appropriately
(there is always prelude on Java methods that implement a native method
with JS varargs that takes care of this).

Yes valid Java code might fail for instance if there is a (instanceof
String[] call, etc).


>
> In case those are correctly handled, and it is important only to tell
> JsInterop about an array of generics  instead of generic representing an
> array, perhaps Vassilis should have another AccessorFunction which handles
> arrays instead? (Actually maye need 3 more, <T, V[]>, <T[], V>, <T[], V[]>,
> so I don't think this is a serious suggestion).
> Otherwise your email seems to suggest that we need a type in
> jsinterop.base for all JS arrays instead of our current situation of
> pretending that java arrays and js arrays are compatible.
>

You can always use Object[], and nothing will fail.


>
> --
>   Colin Alworth
>   co...@colinalworth.com
>
>
>
> On Mon, Jun 26, 2017, at 12:09 PM, 'Roberto Lublinerman' via GWT
> Contributors wrote:
>
> The short answer is that this is also not a bug.
>
> Java arrays are typed, JS arrays are not. So none of the examples you have
> will fully work.
>
> E.g. If you do array instanceof Date[] on an array built in JS filled with
> Dates it will fail.
>
> A native array is best modeled as SomeNativeJsType[] where there are not
> expectations on the contents of the array from the Java perspective.
>
> We would have loved to have a more seamless array JsInterop.
>
>
>
> On Mon, Jun 26, 2017 at 1:31 AM, Vassilis Virvilis <vasv...@gmail.com>
> wrote:
>
> Originally posted in gwt-users.
> The question here is the same with the previous one.
>
> Is this considered a bug? Should I report it as an issue? and if so where?
>
>  Thanks.
>
>
> -- Forwarded message --
> From: *Vassilis Virvilis* <vasv...@gmail.com>
> Date: Fri, Feb 24, 2017 at 2:44 PM
> Subject: jsinterop woes: Part 2: return Double[]
> To: google-web-tool...@googlegroups.com
>
>
> Hi,
>
> I am not sure if it is a bug but it kills my beautiful jsinterop mappings.
> Let's say that I have a native js function (d3.extent) that returns an
> array of something. It may be dates it may be doubles..
>
> This is mapped nicely with
>
> public static native <T, V> V[] extent(T[] data,
> AccessorFunction<T, V> accessor);
>
>
> Where AccessorFunction is
>
> @JsFunction
> public static interface AccessorFunction<T, V> {
> public V get(T d);
> }
>
>
> The above scheme works for Date and other objects but it fails with
> Double. If I specify another variant of d3.extent that returns double[] it
> works
> Here is the javascript exception
>
> Uncaught Error: java.lang.ClassCastException
> at java_lang_ClassCastException_ClassCastException__V.java_lang
> _Throwable_createError__Ljava_lang_String_2Ljava_lang_Object_2 [as
> package_private$java_lang$createError__Ljava_lang_String_2Ljava_lang_Object_2]
> (dashboard-0.js:7245)
> at java_lang_ClassCastException_ClassCastException__V.java_lang
> _Throwable_initializeBackingError__V [as 
> private$java_lang_Throwable$initializeBackingError__V]
> (dashboard-0.js:7300)
> a

Re: [gwt-contrib] Fwd: jsinterop woes: Part 2: return Double[]

['Roberto Lublinerman' via GWT Contributors]

The short answer is that this is also not a bug.

Java arrays are typed, JS arrays are not. So none of the examples you have
will fully work.

E.g. If you do array instanceof Date[] on an array built in JS filled with
Dates it will fail.

A native array is best modeled as SomeNativeJsType[] where there are not
expectations on the contents of the array from the Java perspective.

We would have loved to have a more seamless array JsInterop.



On Mon, Jun 26, 2017 at 1:31 AM, Vassilis Virvilis 
wrote:

> Originally posted in gwt-users.
>
> The question here is the same with the previous one.
>
> Is this considered a bug? Should I report it as an issue? and if so where?
>
>  Thanks.
>
>
> -- Forwarded message --
> From: Vassilis Virvilis 
> Date: Fri, Feb 24, 2017 at 2:44 PM
> Subject: jsinterop woes: Part 2: return Double[]
> To: google-web-tool...@googlegroups.com
>
>
> Hi,
>
> I am not sure if it is a bug but it kills my beautiful jsinterop mappings.
>
> Let's say that I have a native js function (d3.extent) that returns an
> array of something. It may be dates it may be doubles..
>
> This is mapped nicely with
>
> public static native  V[] extent(T[] data,
>> AccessorFunction accessor);
>>
>
> Where AccessorFunction is
>
> @JsFunction
>> public static interface AccessorFunction {
>> public V get(T d);
>> }
>>
>
> The above scheme works for Date and other objects but it fails with
> Double. If I specify another variant of d3.extent that returns double[] it
> works
>
> Here is the javascript exception
>
> Uncaught Error: java.lang.ClassCastException
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _Throwable_createError__Ljava_lang_String_2Ljava_lang_Object_2 [as
>> package_private$java_lang$createError__Ljava_lang_String_2Ljava_lang_Object_2]
>> (dashboard-0.js:7245)
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _Throwable_initializeBackingError__V [as 
>> private$java_lang_Throwable$initializeBackingError__V]
>> (dashboard-0.js:7300)
>> at 
>> java_lang_ClassCastException_ClassCastException__V.java_lang_Throwable_Throwable__V
>> (dashboard-0.js:7133)
>> at 
>> java_lang_ClassCastException_ClassCastException__V.java_lang_Exception_Exception__V
>> (dashboard-0.js:7381)
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _RuntimeException_RuntimeException__V (dashboard-0.js:29760)
>> at java_lang_ClassCastException_ClassCastException__V
>> (dashboard-0.js:57310)
>> at javaemul_internal_InternalPreconditions_checkCriticalType__ZV
>> (dashboard-0.js:72171)
>> at javaemul_internal_InternalPreconditions_checkType__ZV
>> (dashboard-0.js:72378)
>> at com_google_gwt_lang_Cast_castTo__Ljava_lang_Object_2Lcom_
>> google_gwt_core_client_JavaScriptObject_2Ljava_lang_Object_2
>> (dashboard-0.js:647)
>>
>
> It goes here
>
>> function com_google_gwt_lang_Cast_castTo__Ljava_lang_Object_2Lcom_
>> google_gwt_core_client_JavaScriptObject_2Ljava_lang_Object_2(src_0,
>> dstId){
>>   com_google_gwt_lang_Cast_$clinit__V();
>>   javaemul_internal_InternalPreconditions_checkType__ZV(com_
>> google_gwt_lang_Cast_jsEquals__Ljava_lang_Object_2Ljava_lang_Object_2Z(src_0,
>> null) || com_google_gwt_lang_Cast_canCast__Ljava_lang_Object_2Lcom_
>> google_gwt_core_client_JavaScriptObject_2Z(src_0, dstId));
>>   return src_0;
>> }
>>
>
> Arguments:
>
>- src_0:
>   - evaluated: js array of numbers as it should be
>   - dstId:
>   - evaluated: 2396
>
> and then it goes to
>
> function com_google_gwt_lang_Cast_canCast__Ljava_lang_Object_2Lcom_
>> google_gwt_core_client_JavaScriptObject_2Z(src_0, dstId){
>>   com_google_gwt_lang_Cast_$clinit__V();
>>   if (com_google_gwt_lang_Cast_instanceOfString__Ljava_lang_Object_2Z(src_0))
>> {
>> return !!com_google_gwt_lang_Cast_stringCastMap[dstId];
>>   }
>>else if (src_0.java_lang_Object_castableTypeMap) {
>> return !!src_0.java_lang_Object_castableTypeMap[dstId];
>>   }
>>else if 
>> (com_google_gwt_lang_Cast_instanceOfDouble__Ljava_lang_Object_2Z(src_0))
>> {
>> return !!com_google_gwt_lang_Cast_doubleCastMap[dstId];
>>   }
>>else if 
>> (com_google_gwt_lang_Cast_instanceOfBoolean__Ljava_lang_Object_2Z(src_0))
>> {
>> return !!com_google_gwt_lang_Cast_booleanCastMap[dstId];
>>   }
>>   return false;
>> }
>>
>
> where it fails.
>
> Would it be possible to handle transparently also Double[] (and possibly
> String[])? as double[]?
>
>Thank you for reading that far...
>
> Vassilis
>
>
>
>
>
>
>
> --
> Vassilis Virvilis
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 

Re: [gwt-contrib] Fwd: jsinterop woes: Part 1: instanceof function in generics casting

['Roberto Lublinerman' via GWT Contributors]

The declaration

  package somepackage;

  @JsNative(isTrue, name = "ordinal")
  class Ordinal {
  
  }

effectively says that there is a native type "somepackage.ordinal", which
d3.ordinal is not.

You can model it as a native interface for example where there is not such
expectation.

So as I understand your report this is not a bug but just an error in
modellin

On Sat, Jun 24, 2017 at 7:58 AM, Vassilis Virvilis 
wrote:

> Originally posted in gwt-users.
>
> Two questions:
>
>1. Do you want me to report it as a bug somewhere? and where that
>would be?
>2. I have two more. Do you want me to post them here or this is not
>the right place to post at all?
>
>
>
> -- Forwarded message --
> From: Vassilis Virvilis 
> Date: Fri, Feb 24, 2017 at 2:26 PM
> Subject: jsinterop woes: Part 1: instanceof function in generics casting
> To: google-web-tool...@googlegroups.com
>
>
> Hi,
>
> again I don't know if this is a bug but it hurts my style
>
> D3 defines d3.scale.ordinal as both a function and an object.
> $wnd.d3.scale.ordinal returns function() in the browser's console though
>
>
>@JsType(isNative = true, name = "ordinal")
>>   public static class Ordinal {
>>/** @todo TODO: this crashes. Why? */
>>public native  O range(I[] values);   // this
>> doesn't work
>>//public native  Ordinal range(I[] values); // this works
>>   }
>>
>
> I want the generic type because then I can put it in a base class and
> share some code.
>
> I am using it like this
>
>> D3.Scale.Ordinal color = D3.Scale.ordinal().range(new String[]
>> {"#98abc5", "#8a89a6"});
>>
>
> Here is the javascript exception:
>
> Error: java.lang.ClassCastException
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _Throwable_createError__Ljava_lang_String_2Ljava_lang_Object_2 [as
>> package_private$java_lang$createError__Ljava_lang_String_2Ljava_lang_Object_2]
>> (dashboard-0.js:7245)
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _Throwable_initializeBackingError__V [as 
>> private$java_lang_Throwable$initializeBackingError__V]
>> (dashboard-0.js:7300)
>> at 
>> java_lang_ClassCastException_ClassCastException__V.java_lang_Throwable_Throwable__V
>> (dashboard-0.js:7133)
>> at 
>> java_lang_ClassCastException_ClassCastException__V.java_lang_Exception_Exception__V
>> (dashboard-0.js:7381)
>> at java_lang_ClassCastException_ClassCastException__V.java_lang
>> _RuntimeException_RuntimeException__V (dashboard-0.js:29724)
>> at java_lang_ClassCastException_ClassCastException__V
>> (dashboard-0.js:57274)
>> at javaemul_internal_InternalPreconditions_checkCriticalType__ZV
>> (dashboard-0.js:72135)
>> at javaemul_internal_InternalPreconditions_checkType__ZV
>> (dashboard-0.js:72342)
>> at com_google_gwt_lang_Cast_castToNative__Ljava_lang_Object_2Lc
>> om_google_gwt_core_client_JavaScriptObject_2Ljava_lang_Object_2
>> (dashboard-0.js:707)
>>
>
> In
>
>> function com_google_gwt_lang_Cast_castToNative__Ljava_lang_Object_2Lc
>> om_google_gwt_core_client_JavaScriptObject_2Ljava_lang_Object_2(src_0,
>> jsType){
>>   com_google_gwt_lang_Cast_$clinit__V();
>>   javaemul_internal_InternalPreconditions_checkType__ZV(com_go
>> ogle_gwt_lang_Cast_jsEquals__Ljava_lang_Object_2Ljava_lang_Object_2Z(src_0,
>> null) || com_google_gwt_lang_Cast_jsinstanceOf__Ljava_lang_Object_2Lc
>> om_google_gwt_core_client_JavaScriptObject_2Z(src_0, jsType));
>>   return src_0;
>> }
>>
>
> Arguments:
>
>- src_0:
>   - passed:
>   - evaluated: function scale(x)
>- jsType:
>   - passed: $wnd.scale.ordinal
>   - evaluated: function anonymous()
>
> The reason it fails is that
>
>> function com_google_gwt_lang_Cast_jsinstanceOf__Ljava_lang_Object_2Lc
>> om_google_gwt_core_client_JavaScriptObject_2Z(obj, jsType){
>>   com_google_gwt_lang_Cast_$clinit__V();
>>   return obj && (jsType && obj instanceof jsType);
>> }
>>
>
> obj is src_0 != null and jsType = function anonymous() != null but (obj
> instanceof jsType) === false
>
> Any idea about that?
>
> --
> Vassilis Virvilis
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/google-web-toolkit-contributors/CAKbOjEx1v%3D-%3DVHd0Z5p
> cgTbKTPzFktR7nxoCx2Sr9yutZHtxiw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 

Re: [gwt-contrib] Re: Elemental2 and JsInterop base beta releases available.

['Roberto Lublinerman' via GWT Contributors]

We relaxed restriction checking to allow void return type from getters.

Cl is up for review:
https://gwt-review.googlesource.com/#/c/18020/



On Thu, Apr 6, 2017 at 3:17 PM, Jens  wrote:

> Hmm, I have just built gwt head from source and used the above jars but
> SDM tells me:
>
>  Errors in jsinterop/base/Js.java
>  [ERROR] Line 56: JsProperty 'void Js.debugger()' should have a
> correct setter or getter signature.
>
>
> Can anyone confirm?
>
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/d460f0fb-6519-
> 4eab-869b-4838e51077ad%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DWL%2BNy5%2BSpQ4H9Xrho-3hMRs8fO68C9bxwUZzkTi20_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Errors in com/google/gwt/emul/java/lang/String.java

['Roberto Lublinerman' via GWT Contributors]

You probably have a misconfigured class path. The symptoms are consistent
with trying to compile rc3 GWT SDK emulation library with an rc2 compiler.

On Thu, Oct 13, 2016 at 10:05 AM, Teletin Alin 
wrote:

> Forgot to say that with:
>>
> The pom.xml versions for gwt:
> 2.8.0-rc2-patched
> 2.8.0-rc2
>
> it works. So, the problem is in rc3.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/c1bb53f0-959d-
> 4845-95bf-1a33b547c6f6%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmB_qgCpOP%2B-qf%3D-fwE8FYJgW4iGgWAedWRYQ6Lqu1D4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] SNAPSHOT of 21 Sept breaks my build (invalid namespace

['Roberto Lublinerman' via GWT Contributors]

The error suggests a class path issue. The same patch that introduced
 in native string relaxed the checking for namespaces in the
compiler to allow this situation (
https://gwt-review.googlesource.com/#/c/16881/).

On Wed, Sep 21, 2016 at 2:46 AM, stuckagain  wrote:

> It looks like some changes to JSInterop are breaking my build
>
> Compiling module com.swift.common.paging.PagingTest.JUnit
>Ignored 1 unit with compilation errors in first pass.
> Compile with -strict or with -logLevel set to TRACE or DEBUG to see all
> errors.
>Errors in com/google/gwt/emul/java/lang/String.java
>   [ERROR] Line 165: 'String.NativeFunction 
> String.getFromCharCodeFunction()'
> has invalid namespace ''.
>   [ERROR] Line 757: 'String.NativeString' has invalid namespace
> ''.
>
> Additionally, how can I enable strict mode for GWTTestCases when using
> tbroyer's maven plugin ?
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/5e035a47-ff94-
> 4bfa-869e-fee8fb1dd0fc%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmZYsv%3DEknBAVUvsS_Dv_TKYex9dHD39G%2B3-tKT6Qf0wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

['Roberto Lublinerman' via GWT Contributors]

Arnaud, have you tried using -strict? GWT ignores compilation units with
errors if they are not explicitly reachable from the entry point. I assume
your Toto class is only referenced from JS. So if this class has any
compile error (like missing references) then GWT does not see the class,
much less know it is a JsType. Strict mode should give you an error in this
case.

On Fri, Sep 9, 2016 at 6:09 AM, Arnaud TOURNIER  wrote:

> I have one problem which is recurring, related to JsInterop.
>
> Sometimes the JsInterop JS stub is not generated because of (seemingly) an
> internal error in SuperDevMode (and GWTC it seems), but nothing is logged,
> so it's difficult to diagnose.
>
> For example, in an application (which does not inherits the User module),
> when i write a class like this, the JS stub is generated correctly :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> // really nothing here...
> }
> }
>
> But if i change it to :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> Window.alert( "yeah" );
> }
> }
>
> Then the JS stub is not generated (i mean the Toto constructor function is
> not made available to JS scope).
>
> I understand that Window.alert(...) is implemented in the User module and
> since i don't inherit from it, the thing cannot be generated. But no
> message is generated (neither by SDM nor by the GWTC if i remember well),
> which is then difficult to diagnose...
>
> Note : i should be able to produce a minimal repro case for this thing.
>
>
> Then sometimes, a @JsInterop class would not be exported to JS, but if i
> change its name then it's generated, which is... weird.
>
> For this one i am not sure i can give a minimal repro case because it
> happens on quite large projects (angular2 with gwt 2.8)...
>
>
> I saw another error:
>
> It was in a @JsInterop class, which called a template method (i mean with
>  in the signature of the method). I had to specify the  type to call
> it to have the SDM generating the class. If i didn't, the javac would infer
> correctly the  type (so no error appears in the IDE, which is Eclipse in
> my case), but it seemed that SDM did not manage to infer the type correctly
> because then the class would not be accessible from javascript... I can
> give you a sample file if you need.
>
>
> A last one : i tried migrating a big app from 2.7 to 2.8-rc2 (same problem
> with previous sub versions of the 2.8). The compiler goes on compiling then
> does the linking, but it suddenly crashes without saying anything (i tried
> TRACE and DEBUG log levels with no more useful information) and results in
> a maven build failure. The build is happening in maven. Since the app is
> quite big, i guess the problem comes from a dependency i use which is not
> 2.8 friendly (did not have enough time to investigate that deeply). But
> again, the problem is not that the compile does not work, but that no
> useful message is generated to understand the error.
>
> For this one, i can give you the code, but privately since it is a
> business app that is not open source...
>
> Thanks !
>
> Arnaud Tournier
> LTE Consulting
>
>
> Le jeudi 8 septembre 2016 16:27:36 UTC+2, Daniel Kurka a écrit :
>>
>> Hi all,
>>
>> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email
>> with any outstanding reviews that you want to see included.
>>
>> -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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/5e5b6585-aba1-
> 48ce-a5d6-6f9a702e801b%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DOvF6Bu%2BmFdYDmNF2F11zQgDxdFo65j6zTYnWFQr2ZXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

['Roberto Lublinerman' via GWT Contributors]

The issue was addressed post beta 1. Please use the 2.8rc1 instead.

On Thu, Aug 4, 2016 at 6:57 PM, Mark Duesbury <mark.duesb...@defcloud.com>
wrote:

> Just tried with -Xmx8g (running on 16gb Macbook Pro)
>
> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
>
> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.createType(Ref
> erenceMapper.java:280)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.ReferenceMapper.get(ReferenceM
> apper.java:146)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createField(GwtA
> stBuilder.java:3900)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.createMembers(Gw
> tAstBuilder.java:3969)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.processImpl(GwtA
> stBuilder.java:3825)
>
> [ERROR] at com.google.gwt.dev.jjs.impl.GwtAstBuilder.process(GwtAstBu
> ilder.java:3860)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder$
> CompileMoreLater$UnitProcessorImpl.process(Comp
> ilationStateBuilder.java:129)
>
> [ERROR] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(
> JdtCompiler.java:384)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.Compiler.
> processCompiledUnits(Compiler.java:546)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.Compiler.compile(Comp
> iler.java:458)
>
> [ERROR] at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompi
> ler.java:1089)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder$
> CompileMoreLater.compile(CompilationStateBuilder.java:325)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(
> CompilationStateBuilder.java:548)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
> CompilationStateBuilder.java:479)
>
> [ERROR] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(
> CompilationStateBuilder.java:465)
>
> [ERROR] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(
> ModuleDef.java:423)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:222)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
>
> [ERROR] at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
>
> [ERROR] at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
>
> [ERROR] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
>
> [ERROR] at com.google.gwt.dev.CompileTaskRunner.doRun(Compil
> eTaskRunner.java:55)
>
> [ERROR] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(
> CompileTaskRunner.java:50)
>
> [ERROR] at com.google.gwt.dev.Compiler.main(Compiler.java:125)
>
> Full GWT Maven Plugin config
>
> 
>
> 
>
> org.codehaus.mojo
>
> gwt-maven-plugin
>
> 2.8.0-beta1
>
> 
>
> 
>
> com.google.gwt
>
> gwt-user
>
> ${gwtversion}
>
> 
>
> 
>
> com.google.gwt
>
> gwt-dev
>
> ${gwtversion}
>
> 
>
> 
>
> com.google.gwt
>
> gwt-servlet
>
> ${gwtversion}
>
> 
>
> 
>
> 
>
> 
>
> 
>
>   -Xms1024M -Xmx8g -Xss1024k
>
> 
>
> 
>
> compile
>
> 
>
> 
>
> 
>
> 
>
> desktop.html
>
> ${project.build.directory}/${project.build.finalName} hostedWebapp>
>
> true
>
> true
>
> true
>
> INFO
>
> 
>
> 
>
> It works fine if I switch back to GWT 2.7.0
>
> On Thursday, August 4, 2016 at 10:13:40 PM UTC+1, Roberto Lublinerman
> wrote:
>>
>> You might need to increase the heap size. JDT still uses more memory
>> under Java 8 which is the source level that is currently supported by GWT
>> (try -Xmx3g or  -Xmx4g).
>>
>> On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury <mark.d...@defcloud.com>
>> wrote:
>>
>>> Hi .. Thanks for the rc...
>>>
>>> I have been struggling for a while now with a
>>> java.lang.OutOfMemoryError: GC overhead limit exceeded error on compilation
>>> since switching to GWT 2.8.0 beta1. I thought and hoped the problem would
>>> be solved with the release of the RC, but it hasn't. I have searched high
>>> and low on stackoverflow and elsewhere and tried just about every
>>> combination of jvm settings I could find.. but nothing works. I dont think
>>> my project is that large with 215 source files.
>>>
>>> The last settings I tried were...
>>>
>>> 
>>>
>

Re: [gwt-contrib] Re: GWT 2.8.0 RC1 is here!

['Roberto Lublinerman' via GWT Contributors]

You might need to increase the heap size. JDT still uses more memory under
Java 8 which is the source level that is currently supported by GWT (try
-Xmx3g or  -Xmx4g).

On Thu, Aug 4, 2016 at 11:27 AM, Mark Duesbury 
wrote:

> Hi .. Thanks for the rc...
>
> I have been struggling for a while now with a java.lang.OutOfMemoryError:
> GC overhead limit exceeded error on compilation since switching to GWT
> 2.8.0 beta1. I thought and hoped the problem would be solved with the
> release of the RC, but it hasn't. I have searched high and low on
> stackoverflow and elsewhere and tried just about every combination of jvm
> settings I could find.. but nothing works. I dont think my project is that
> large with 215 source files.
>
> The last settings I tried were...
>
> 
>
> 
>
> 
>
> 4
>
>   -Xmx2g -Xms1g -Xss1024k
>
>   true
>
> 
>
> 
>
> compile
>
> 
>
> 
>
> 
>
>
> The error occurs at different points in the compile cycle... A few samples
> are shown below...
>
> [ERROR] Exception in thread "main" java.lang.OutOfMemoryError: GC overhead
> limit exceeded
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.BoundSet.(
> BoundSet.java:308)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.
> createInitialBoundSet(InferenceContext18.java:230)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.
> ConstraintExpressionFormula.inferInvocationApplicability(C
> onstraintExpressionFormula.java:336)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.InferenceContext18.
> inferInvocationApplicability(InferenceContext18.java:370)
>
> [ERROR] at org.eclipse.jdt.internal.compiler.lookup.
> ParameterizedGenericMethodBinding.computeCompatibleMethod18(
> ParameterizedGenericMethodBinding.java:233)
>
>
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/1c185f70-edf4-
> 4e54-9cfe-48b7908d54ba%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3Dx45KNani6eccA9MUejj%2BGNOOPcduVaf%3D-Gx9b0fQxhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Experimental release of Elemental2

['Roberto Lublinerman' via GWT Contributors]

Looking at the elemental code that uses a lambda which will not be
EventHandler but a JsFunction. Could you try with an anonymous EventHandler
instead?

On Tue, Aug 2, 2016 at 1:51 AM, Steve Andrews 
wrote:

> I've created a quick test project and put it at
> https://github.com/steveandrews01/JsInteropTest
>
> The click listener only works if compiled with the flag set. If I run it
> without the flag and inspect the DOM in Chrome then the event listener is
> not attached to the button.
>
> (Changing the flag needs a SDM cache clear!)
>
> Steve
>
>
> On Monday, 1 August 2016 20:48:13 UTC+1, Goktug Gokdogan wrote:
>>
>> Can you share a small repro for this? (EventListener requiring
>> generateJsInteropExports)
>>
>> On Thu, Jul 28, 2016 at 12:27 AM, Steve Andrews 
>> wrote:
>>
>>> I've done some more testing and cleared my cache and can still only get
>>> EventListener to work with the generateJsInteropExports flag set.
>>>
>>> I've had another problem with EventListener on a select element but I'm
>>> using an external framework for my project (Materialize) and think that
>>> it's their framework that doesn't like the EventListener object. If I use a
>>> standard select element then it's working. I can get around this by adding
>>> the listener through a JQuery wrapper so no problem.
>>>
>>> I've also found that Window.location returns an Object - will this be
>>> sorted in a future release?
>>>
>>> Other than that Elemental is working well so far! Nice work!
>>>
>>> Steve
>>>
>>> On Friday, 22 July 2016 11:31:24 UTC+1, Jens wrote:


 It only works with the generateJsInteropExports flag set though.
>

 Sounds like a bug to me.

 -- J.

>>> --
>>> 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-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/16498b97-7d3d-44c7-b42b-e40be9de1e26%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fca60fc6-7cfd-44ea-9728-295c77293d74%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnEftgbDyZ9_6hqQMonpyLoQW80YcX706jtPGYntKXx2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

['Roberto Lublinerman' via GWT Contributors]

I filed a bug with a minimal repro at
https://github.com/gwtproject/gwt/issues/9379 and uploaded a fix for review
at https://gwt-review.googlesource.com/#/c/15450

On Wed, Jul 20, 2016 at 11:23 AM, Roberto Lublinerman <rlu...@google.com>
wrote:

> Could you guys file an issue for this to keep track of it?
>
> On Wed, Jul 20, 2016 at 10:34 AM, Roberto Lublinerman <rlu...@google.com>
> wrote:
>
>> It should read setJsOverlay() but that would not fix the error. I think I
>> understand why it might be happening but it would be nice if we have a
>> small repro case.
>>
>> On Wed, Jul 20, 2016 at 6:42 AM, Thomas Broyer <t.bro...@gmail.com>
>> wrote:
>>
>>> +rluble
>>>
>>> Could you set a breakpoint in JjsUtils trying to understand what causes
>>> the NPE? (what is null, which method is being processed, and what it looks
>>> like in your code)
>>> Reading the code, I wonder if
>>> https://github.com/gwtproject/gwt/blob/master/dev/core/src/com/google/gwt/dev/jjs/impl/JjsUtils.java#L165
>>> should read setJsOverlay() instead of isJsOverlay()
>>>
>>>
>>> On Wednesday, July 20, 2016 at 2:23:01 PM UTC+2, stuckagain wrote:
>>>>
>>>>
>>>> I was reviving a project that I was working on, which was using 2.8
>>>> snapshot.
>>>> It was working fine a few months ago but now the GWT compilation is
>>>> failing.
>>>> No code was changed in the meantime, so my guess is that something
>>>> changed in the GWT compiler that I need to know about ?
>>>>
>>>> Any idea how I can track the actual reason why the compiler is crashing
>>>> ?
>>>>
>>>> [INFO] [ERROR] Unexpected internal compiler error
>>>>
>>>> [INFO] java.lang.NullPointerException
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.impl.JjsUtils.createForwardingMethod(JjsUtils.java:181)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.impl.ComputeOverridesAndImplementDefaultMethods.maybeAddSyntheticOverride(ComputeOverridesAndImplementDefaultMethods.java:276)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.impl.ComputeOverridesAndImplementDefaultMethods.computeOverrides(ComputeOverridesAndImplementDefaultMethods.java:150)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.impl.ComputeOverridesAndImplementDefaultMethods.exec(ComputeOverridesAndImplementDefaultMethods.java:78)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.impl.UnifyAst.computeOverrides(UnifyAst.java:1071)
>>>>
>>>> [INFO] at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:900)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1410)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1222)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:1140)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:255)
>>>>
>>>> [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:255)
>>>>
>>>> [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:202)
>>>>
>>>> [INFO] at com.google.gwt.dev.Precompile.precompile(Precompile.java:143)
>>>>
>>>> [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:204)
>>>>
>>>> [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:155)
>>>>
>>>> [INFO] at com.google.gwt.dev.Compiler.compile(Compiler.java:144)
>>>>
>>>> [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
>>>>
>>>> [INFO] at
>>>> com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
>>>>
>>>> [INFO] at com.google.gwt.dev.Compiler.main(Compiler.java:125)
>>>>
>>>
>>
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmQNLLag%3DmO534wQ%3D6J%3DEeiedeDdzi7ZJbqX4N5AyvMRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issues with GWT 2.8 snapshot

['Roberto Lublinerman' via GWT Users]

The error messages were introduced by mistake in the JSNI error reporting 
fix (https://gwt-review.googlesource.com/#/c/15080) and the fix for those 
is up for review https://gwt-review.googlesource.com/#/c/15120/

On Thursday, June 9, 2016 at 8:55:36 AM UTC-7, Hristo Stoyanov wrote:
>
> Thomas, yes, it is a javadoc failure, and it is still there. I just 
> re-tried.
>
> On Thursday, June 9, 2016 at 5:40:24 AM UTC-7, Thomas Broyer wrote:
>>
>> I see Hristo's error is in a "javadoc" task, could it be the same (or 
>> similar) for you?
>>
>> On Thursday, June 9, 2016 at 1:18:02 PM UTC+2, Filipe Sousa wrote:
>>>
>>> Done that and still have the same errors. Despite the errors the project 
>>> works as if had no errors
>>>
>>> $ java -version
>>> java version "1.8.0_92"
>>> Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
>>> Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)
>>>
>>> $ ant -version
>>> Apache Ant(TM) version 1.9.7 compiled on April 9 2016
>>>
>>> On Thursday, June 9, 2016 at 11:50:47 AM UTC+1, Thomas Broyer wrote:

 +rluble, +goktug

 Roberto, Goktug, any idea?
 This comes from one of these changes:
 http://build.gwtproject.org/job/gwt/520/changes
 http://build.gwtproject.org/job/gwt/521/changes

 All: anyone tried to build it locally to make sure it's not due to a 
 corrupted JAR during upload to Sonatype OSSRH?

 On Thursday, June 9, 2016 at 11:40:53 AM UTC+2, Henrik wrote:
>
> Seeing the same problems (maven build).  Worked fine 10 hrs ago 
> though, so the latest snapshot seems hosed. 
>
> Regards,
> Henrik
>
> On Thursday, June 9, 2016 at 8:14:47 AM UTC+2, Hristo Stoyanov wrote:
>>
>> I started getting the following errors with Gradle builds and the 
>> latest GWT 2.8.-SNAPSHOT - any idea ?
>>
>>
>> ===
>>
>>
>> /root/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-user/2.8.0-SNAPSHOT/c7913836bdcf2423552e6355ad17fbd271ac5207/gwt-user-2.8.0-SNAPSHOT.jar(com/google/gwt/user/client/ui/Widget.java):28:
>>  
>> error: cannot access Event
>> import com.google.gwt.user.client.Event;
>>  ^
>>   bad source file: 
>> /root/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-user/2.8.0-SNAPSHOT/c7913836bdcf2423552e6355ad17fbd271ac5207/gwt-user-2.8.0-SNAPSHOT.jar(com/google/gwt/user/client/Event.java)
>> file does not contain class com.google.gwt.user.client.Event
>> Please remove or make sure it appears in the correct subdirectory 
>> of the sourcepath.
>> /root/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-user/2.8.0-SNAPSHOT/c7913836bdcf2423552e6355ad17fbd271ac5207/gwt-user-2.8.0-SNAPSHOT.jar(com/google/gwt/event/shared/HandlerRegistration.java):23:
>>  
>> error: cannot access HandlerRegistration
>> public interface HandlerRegistration extends 
>> com.google.web.bindery.event.shared.HandlerRegistration {
>>   
>>   ^
>>   bad source file: 
>> /root/.gradle/caches/modules-2/files-2.1/com.google.gwt/gwt-user/2.8.0-SNAPSHOT/c7913836bdcf2423552e6355ad17fbd271ac5207/gwt-user-2.8.0-SNAPSHOT.jar(com/google/web/bindery/event/shared/HandlerRegistration.java)
>> file does not contain class 
>> com.google.web.bindery.event.shared.HandlerRegistration
>> Please remove or make sure it appears in the correct subdirectory 
>> of the sourcepath.
>> 2 errors
>> :gwt-errai:javadoc FAILED
>>
>

-- 
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+unsubscr...@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.

Re: [gwt-contrib] get the obfuscated name of a class method in code?

['Roberto Lublinerman' via GWT Contributors]

You could use Impl.getNameOf() (look
at gwt/user/test/com/google/gwt/junit/client/GWTTestCaseStackTraceTest.java
for an example of usage). Note that using this feature will disable some
optimizations on the target function.

That being said, this is an internal functionality and could
change/disappear at any time (I doubt it will still be there in the next
major release). Use at your own risk.

Alternatively you could write some JS (JSNI or otherwise) and use the name
property on the function.

On Tue, Apr 26, 2016 at 7:19 AM, Paul Stockley  wrote:

> Is it possible to get the obfuscated name of a class method in code?
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/8e1afe41-81b8-43d2-a17e-68c94a75514d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnDn4rGneKbmdGFfZnFSH%3Df0omDfBex8XvEZGMV5%3D5dMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

That is why I am saying that it will be easy to do for JsFunctions but due
to Java semantics (regular) lambdas are just not plain functions and thus I
don't think there is much to gain there.

I don't think there is much to gain on the regular lambdas. There are 2
different ways we can handle them and reduce a bit of the generated code
but I don't think there is a lot of potential ways.
1) do not generate anonymous inner classes, rather have the make lambda
factory take all the required parameters, i.e. castmap.
2) create an anonymous innerclass based on the class/interface that is
being extended/implemented when a lambda for that is seen. In that way if
an interface is used with many lambdas there is only one supporting class
instead of many.


On Mon, Apr 18, 2016 at 10:22 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> I understand, but the trampolines cause bloat, and if you're
> suggesting treating all non-JsFunction Java8 lambdas as JsFunctions as
> far as code-gen is concerned, then you would not be able to make the
> following code work:
>
> foo(Callable x) { bar(x); }
> foo(Runnable x) { bar(x); }
>
> bar(Object x) { if (x instanceof Callable) { print("it's a callable");
> } else if (x instanceof Runnable) { print("It's a runnable"); } }
>
> You need a castMap for that.
>
>
> On Mon, Apr 18, 2016 at 10:17 AM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> > The point is that for JsFunctions you DON'T actually need to do the
> > makeLambda(). JsFunction was designed to be able to pass JS functions to
> > JAVA so there is a code path for that and we can exploit it for
> JsFunction
> > lambdas.
> >
> > So x -> 42  + capture will be represented in the JAva AST as
> > class X {
> >   {
> >  .  new X$0(capture);
> >   }
> >   // Synthetic lambda method
> >   int lambda_f(capture, x) {
> >  return 42 + capture;
> >   }
> >
> > // Lambda function implmenetation. Nothing needs to be emitted for this
> in
> > JS
> > class X$0 implements JsFunctionInterface {
> >   capture;
> >   X$0(capture) {
> >this.capture = capture;
> >   }
> >
> >   int m(x) {
> >  X.lambda_f(this.capture, x);
> >   }
> > }
> >
> >
> > In the JS ast we do
> >
> >   new X$0(capture)  -->  function(x) { X.lambda_f(capture, x) }
> >
> > So we don't need makeLambda or anything else; we can just treat
> JsFunciton
> > implementation as if they were functions passed in from JavaScript where
> > object methods will go through the regular trampoline into the "JSO"
> > implementation.
> >
> >
> >
> >
> > On Mon, Apr 18, 2016 at 9:55 AM, 'Ray Cromwell' via GWT Contributors
> > <google-web-toolkit-contributors@googlegroups.com> wrote:
> >>
> >> That seems similar to my proposal, only you're doing it in GenJsAST.
> >> You'll still need to the makeLambda() trick to allow it to work as a
> >> regular obejct as well, with hashCode()/equals()/getClass()
> >> properties, as well as castMap installed. But if you use static method
> >> delegation, the size won't be as ideal if the static method doesn't
> >> inline.
> >>
> >> You want something like x -> 42 + capture to compile to
> >> makeLambda(function(x) { return 42 + capture }, castMap, classLit),
> >> not function(x) { return Class.foo(capture, x); } do you not?
> >>
> >>
> >> On Mon, Apr 18, 2016 at 9:49 AM, 'Roberto Lublinerman' via GWT
> >> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> >> > The scheme I had in mind does not modify much the Java AST
> >> > representation
> >> > but is more in the lowering to the JsAST, basically it boils down the
> >> > the
> >> > following:.
> >> > 1. You create the lambda body as a static method of the class where it
> >> > appears. This static method has all captures as parameters (thiis is
> >> > very
> >> > similar as we are doing today).
> >> > 2. Synthesize an anonymous inner class that implement the JsFunciton
> >> > (also
> >> > same as we are doing now). The compiler in the java phase sees this as
> >> > an
> >> > innerclass.
> >> > 3. Emit the following code for new JsFuncitonimplementation(capture1,
> >> > capture2) as function(par1, par2, parn) ->
> >> > {Class.lambdaFunctionImplemen

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

The point is that for JsFunctions you DON'T actually need to do the
makeLambda(). JsFunction was designed to be able to pass JS functions to
JAVA so there is a code path for that and we can exploit it for JsFunction
lambdas.

So x -> 42  + capture will be represented in the JAva AST as
class X {
  {
 .  new X$0(capture);
  }
  // Synthetic lambda method
  int lambda_f(capture, x) {
 return 42 + capture;
  }

// Lambda function implmenetation. Nothing needs to be emitted for this in
JS
class X$0 implements JsFunctionInterface {
  capture;
  X$0(capture) {
   this.capture = capture;
  }

  int m(x) {
 X.lambda_f(this.capture, x);
  }
}


In the JS ast we do

  new X$0(capture)  -->  function(x) { X.lambda_f(capture, x) }

So we don't need makeLambda or anything else; we can just treat JsFunciton
implementation as if they were functions passed in from JavaScript where
object methods will go through the regular trampoline into the "JSO"
implementation.




On Mon, Apr 18, 2016 at 9:55 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> That seems similar to my proposal, only you're doing it in GenJsAST.
> You'll still need to the makeLambda() trick to allow it to work as a
> regular obejct as well, with hashCode()/equals()/getClass()
> properties, as well as castMap installed. But if you use static method
> delegation, the size won't be as ideal if the static method doesn't
> inline.
>
> You want something like x -> 42 + capture to compile to
> makeLambda(function(x) { return 42 + capture }, castMap, classLit),
> not function(x) { return Class.foo(capture, x); } do you not?
>
>
> On Mon, Apr 18, 2016 at 9:49 AM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> > The scheme I had in mind does not modify much the Java AST representation
> > but is more in the lowering to the JsAST, basically it boils down the the
> > following:.
> > 1. You create the lambda body as a static method of the class where it
> > appears. This static method has all captures as parameters (thiis is very
> > similar as we are doing today).
> > 2. Synthesize an anonymous inner class that implement the JsFunciton
> (also
> > same as we are doing now). The compiler in the java phase sees this as an
> > innerclass.
> > 3. Emit the following code for new JsFuncitonimplementation(capture1,
> > capture2) as function(par1, par2, parn) ->
> > {Class.lambdaFunctionImplementation(capture1, capture2, par1, par2,
> parn) }.
> > 4. Do not emit any code for the anonymous inner class.
> >
> > This function will behave as if it was a native function passed from JS,
> and
> > object methods will work in the same way. Of course the devil is in the
> > details.
> >
> >
> > On Mon, Apr 18, 2016 at 9:34 AM, 'Ray Cromwell' via GWT Contributors
> > <google-web-toolkit-contributors@googlegroups.com> wrote:
> >>
> >> Seems to me this'll be tricky to pull off. The GWT compiler has no
> >> notion of captured scope. If you want to create a class type that
> >> represents a lambda, but which doesn't actually get output as a class,
> >> you'd have to change many many parts of the compiler.
> >>
> >> I think perhaps the best thing you could do would be a kind of
> >> 'peephole' optimization pass. After all Java optimization passes have
> >> run, and after JS has been generated, go through using pattern
> >> matching to find "new generatedlambda(captured variables)" and replace
> >> it with "makeLambda(classtype, castMap, classLiteral, function(...) {
> >> body of single abstract method })". Then hope the JS dead code pruning
> >> removes the unused inner class.
> >>
> >> I think if you try to model this in the Java AST it would impact too
> much
> >> stuff.
> >>
> >>
> >> On Mon, Apr 18, 2016 at 9:04 AM, 'Roberto Lublinerman' via GWT
> >> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> >> > We accept patches :)
> >> >
> >> > On Sun, Apr 17, 2016 at 8:40 PM, Paul Stockley <pstockl...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Given that it will be realistically a couple of years before most
> large
> >> >> projects could migrate to J2CL, it would be really nice to have a
> more
> >> >> optimal code generation for lambda's, especially for JsFunction. When
> >> >> 2.8
> >> >> gets released, I think people will really start taking advantage of
> >>

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

The scheme I had in mind does not modify much the Java AST representation
but is more in the lowering to the JsAST, basically it boils down the the
following:.
1. You create the lambda body as a static method of the class where it
appears. This static method has all captures as parameters (thiis is very
similar as we are doing today).
2. Synthesize an anonymous inner class that implement the JsFunciton (also
same as we are doing now). The compiler in the java phase sees this as an
innerclass.
3. Emit the following code for new JsFuncitonimplementation(capture1,
capture2) as function(par1, par2, parn) ->
{Class.lambdaFunctionImplementation(capture1, capture2, par1, par2, parn)
}.
4. Do not emit any code for the anonymous inner class.

This function will behave as if it was a native function passed from JS,
and object methods will work in the same way. Of course the devil is in the
details.


On Mon, Apr 18, 2016 at 9:34 AM, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Seems to me this'll be tricky to pull off. The GWT compiler has no
> notion of captured scope. If you want to create a class type that
> represents a lambda, but which doesn't actually get output as a class,
> you'd have to change many many parts of the compiler.
>
> I think perhaps the best thing you could do would be a kind of
> 'peephole' optimization pass. After all Java optimization passes have
> run, and after JS has been generated, go through using pattern
> matching to find "new generatedlambda(captured variables)" and replace
> it with "makeLambda(classtype, castMap, classLiteral, function(...) {
> body of single abstract method })". Then hope the JS dead code pruning
> removes the unused inner class.
>
> I think if you try to model this in the Java AST it would impact too much
> stuff.
>
>
> On Mon, Apr 18, 2016 at 9:04 AM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
> > We accept patches :)
> >
> > On Sun, Apr 17, 2016 at 8:40 PM, Paul Stockley <pstockl...@gmail.com>
> wrote:
> >>
> >> Given that it will be realistically a couple of years before most large
> >> projects could migrate to J2CL, it would be really nice to have a more
> >> optimal code generation for lambda's, especially for JsFunction. When
> 2.8
> >> gets released, I think people will really start taking advantage of
> existing
> >> JS libraries that really heavily use functions.
> >>
> >>
> >> On Friday, April 15, 2016 at 12:03:12 PM UTC-4, Roberto Lublinerman
> wrote:
> >>>
> >>> It should not be hard to make JsFunction lambdas more terse, but there
> >>> are no plans for GWT 2.x.
> >>>
> >>>
> >> --
> >> 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-contributors+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> >>
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/d75d8079-463a-4334-8c3c-75f11cc9ab20%40googlegroups.com
> .
> >>
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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-contributors+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DkH9YQjA_P02ibv-Fg4u-gRW6s4Ojm6S2KgTK0KDOYmQ%40mail.gmail.com
> .
> >
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7csJ3vykGQ1rt%2BSTZtYL0cwjMH8zzY0zgiHszfETPg4Dw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gngwS13pEuSHWSMZAtcScTPwuH8tKRNGT7fQMBxa_S2jQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

We accept patches :)

On Sun, Apr 17, 2016 at 8:40 PM, Paul Stockley <pstockl...@gmail.com> wrote:

> Given that it will be realistically a couple of years before most large
> projects could migrate to J2CL, it would be really nice to have a more
> optimal code generation for lambda's, especially for JsFunction. When 2.8
> gets released, I think people will really start taking advantage of
> existing JS libraries that really heavily use functions.
>
>
> On Friday, April 15, 2016 at 12:03:12 PM UTC-4, Roberto Lublinerman wrote:
>>
>> It should not be hard to make JsFunction lambdas more terse, but there
>> are no plans for GWT 2.x.
>>
>>
>> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/d75d8079-463a-4334-8c3c-75f11cc9ab20%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/d75d8079-463a-4334-8c3c-75f11cc9ab20%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DkH9YQjA_P02ibv-Fg4u-gRW6s4Ojm6S2KgTK0KDOYmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

It should not be hard to make JsFunction lambdas more terse, but there are
no plans for GWT 2.x.

On Fri, Apr 15, 2016 at 8:25 AM, Paul Stockley <pstockl...@gmail.com> wrote:

> Are there plans to optimize this in the GWT2.x version in the future?
>
> On Friday, April 15, 2016 at 10:57:00 AM UTC-4, Roberto Lublinerman wrote:
>>
>> Yes, right now all lambdas are implemented as anonymous inner classes,
>> even the ones implementing JsFunction interfaces.
>>
>> On Fri, Apr 15, 2016 at 6:11 AM, Paul Stockley <pstoc...@gmail.com>
>> wrote:
>>
>>> Am I right in saying that java 8 lambda's under the covers is
>>> implemented as an anonymous inner class? Is this also true for SAM
>>> interfaces annotated with JsFunction annotated interfaces?
>>>
>>> --
>>> 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-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/369a5094-7e64-4351-b1e5-16ff5a3a2468%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/369a5094-7e64-4351-b1e5-16ff5a3a2468%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/9fce9c7d-b956-4fcf-b16a-8d25ffb69e57%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/9fce9c7d-b956-4fcf-b16a-8d25ffb69e57%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkM79fnvDifARSkbzp-Gmf2MRHbbtLsXwO0UGYjVubWiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Lambda overhead

['Roberto Lublinerman' via GWT Contributors]

Yes, right now all lambdas are implemented as anonymous inner classes, even
the ones implementing JsFunction interfaces.

On Fri, Apr 15, 2016 at 6:11 AM, Paul Stockley  wrote:

> Am I right in saying that java 8 lambda's under the covers is implemented
> as an anonymous inner class? Is this also true for SAM interfaces annotated
> with JsFunction annotated interfaces?
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/369a5094-7e64-4351-b1e5-16ff5a3a2468%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3Dmk7%3D5pDQhYdWfe8F70cfoWLE6C%2BrifMudXF_SWDosLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Can't run SourceMapTest in Eclipse

['Roberto Lublinerman' via GWT Contributors]

I am not sure what should be included. I use our internal setup that has
all those targets configured correctly already. In the open source build I
normally build the distributions and then inlcude gwt-dev.jar and
gwt-user.jar, IIRC.

On Wed, Apr 6, 2016 at 2:24 PM, Michael Zhou 
wrote:

> Got:
> Loading inherited module 'com.google.gwt.sample.hello.Hello'
>Loading inherited module 'com.google.gwt.user.User'
>   Loading inherited module 'com.google.gwt.event.Event'
>  Loading inherited module 'com.google.gwt.dom.DOM'
> Loading inherited module 'com.google.gwt.safehtml.SafeHtml'
>Loading inherited module 'com.google.gwt.http.HTTP'
>   Loading inherited module
> 'com.google.gwt.xhr.XMLHttpRequest'
>  Loading inherited module
> 'com.google.gwt.typedarrays.TypedArrays'
> Loading inherited module
> 'com.google.gwt.useragent.UserAgent'
>[ERROR] Line 26: Unable to load class
> 'com.google.gwt.useragent.rebind.UserAgentPropertyGenerator'
> java.lang.ClassNotFoundException:
> com.google.gwt.useragent.rebind.UserAgentPropertyGenerator
>
> I think my classpath has included all the folders needed:
> gwt-dev/core/super/
> gwt-dev/core/test/
> gwt-user/core/super/
> gwt-user/core/src/
> gwt-user/core/test-super/
> gwt/user/core/test/
> Hello/core/
> gwt-dev/
>
> Found https://groups.google.com/forum/#!topic/repo-discuss/LpzJZv1GGvI
> but didn't see a solution there.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a43d2e44-5b20-4897-b234-9975b2130da3%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gm1ocX9bLL-Syg6uirzva7LEv9P7Px9H%2BOfPSuJKQGsMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] CodeServer and Compiler broken after "Redo file watching refactor." change

['Roberto Lublinerman' via GWT Contributors]

The fix for this issue is up for review at
https://gwt-review.googlesource.com/#/c/13956

On Wed, Nov 11, 2015 at 1:53 AM, Lars <lars.gemeinha...@gmail.com> wrote:

> It fails for Java 7 and 8 for Windows 7 and 8 ...
> I checked also with the latest ant version and your flag
> "-Dgwt.watchFileChanges=true" and in addition with
> "-Dgwt.persistentunitcache=false" - but no success...
>
> How can I help you? Because for me it's easy to run it on windows :-)
>
> Btw. the issue is also within the 2.8.0-beta1 - this should break all the
> windows builds :-(
>
> E:\gwt-2.8.0-beta1\samples>ant.bat build
> Buildfile: E:\gwt-2.8.0-beta1\samples\build.xml
>
> build:
>
> -do:
>
> libs:
>  [copy] Copying 1 file to
> E:\gwt-2.8.0-beta1\samples\DynaTable\war\WEB-INF\lib
>  [copy] Copying 1 file to
> E:\gwt-2.8.0-beta1\samples\DynaTable\war\WEB-INF\lib
>
> javac:
> [javac] E:\gwt-2.8.0-beta1\samples\DynaTable\build.xml:31: warning:
> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set
> to false for repeatable builds
>  [copy] Copying 2 files to
> E:\gwt-2.8.0-beta1\samples\DynaTable\war\WEB-INF\classes
>
> gwtc:
>  [java] Compiling module com.google.gwt.sample.dynatable.DynaTable
>  [java]Finding entry point classes
>  [java]   [ERROR] Hint: Check the inheritance chain from your
> module; it may not be inheriting a required module or a module may not be
> adding its source path entries properly
>
> BUILD FAILED
> E:\gwt-2.8.0-beta1\samples\build.xml:12: The following error occurred
> while executing this line:
> E:\gwt-2.8.0-beta1\samples\build.xml:4: The following error occurred while
> executing this line:
> E:\gwt-2.8.0-beta1\samples\DynaTable\build.xml:40: Java returned: 1
>
> Total time: 11 seconds
>
> Am Mittwoch, 11. November 2015 08:30:53 UTC+1 schrieb Roberto Lublinerman:
>>
>> It happens in windows with or without the flag I think. I run it with
>> logLevel DEBUG and -string and it was failing to find the sources for
>> javax.validation. But it is a real pain to setup an environment in windows
>> that runs our build. Elemental also fails to build.
>>
>> On Tue, Nov 10, 2015 at 10:36 PM, 'Goktug Gokdogan' via GWT Contributors
>> <google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> Also is this happening in any other configuration? Java8? windows 10?
>>>
>>> I can't reproduce it with mac or linux.
>>>
>>>
>>> On Tue, Nov 10, 2015 at 9:39 PM, 'Roberto Lublinerman' via GWT
>>> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
>>>> Could you run it with -Dgwt.watchFileChanges=false and let us know?
>>>> That flag should turn of the file watching logic.
>>>>
>>>> On Tue, Nov 10, 2015 at 6:39 AM, Lars <lars.gem...@gmail.com> wrote:
>>>>
>>>>> After the "Redo file watching refactor." change
>>>>> (d746d952defbd42c81317ccbd5da0f1561b81d36) both CodeServer and Compiler 
>>>>> are
>>>>> broken for my project and also for the following build in samples (see
>>>>> below).
>>>>> What went wrong?
>>>>> Btw. I'm using Windows7 and Java7...
>>>>>
>>>>> Buildfile: C:\Projects2\gwt-git\samples\build.xml
>>>>> build:
>>>>> -do:
>>>>> dynatable:
>>>>> check.build.type:
>>>>> source:
>>>>> [mkdir] Created dir:
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
>>>>>  [copy] Copying 15 files to
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
>>>>> [mkdir] Created dir:
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
>>>>>  [copy] Copying 4 files to
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
>>>>> serverlibs:
>>>>> [mkdir] Created dir:
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\lib
>>>>> compile:
>>>>> [mkdir] Created dir:
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
>>>>> [gwt.javac] Compiling 13 source files to
>>>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
>>>>> [gwt.javac] Note: Some input files use or override a deprecated API.
>>>>> [gwt.javac] Note: Recompile with -Xlint:deprecation for details.
>>>>> gwtc:
>>>&g

Re: [gwt-contrib] Re: New JsInterop document

['Roberto Lublinerman' via GWT Contributors]

No plan to support through Java implementors, although there are plans to
support varargs which would let you accomplish something similar.
On Nov 10, 2015 08:53, "Manuel Carrasco Moñino"  wrote:

> I see, it works, thanks.
>
> Any plan to work as well with gwt exported classes ?
>
> On Tue, Nov 10, 2015 at 5:33 PM, Julien Dramaix 
> wrote:
>
>> Method overloading works in native JsType JsType(isNative=true)
>>
>> On Tue, Nov 10, 2015 at 5:15 PM Manuel Carrasco Moñino 
>> wrote:
>>
>>> Seems that method overloading is not working anymore with JS_RC mode, it
>>> was working in JS mode though:
>>>
>>> Example:
>>>
>>>boolean validate()
>>>boolean validate(String foo)
>>>
>>> Is it a feature not implemented yet, or it is not in the specification?
>>>
>>> Thanks
>>> - Manolo
>>>
>>>
>>> On Mon, Nov 9, 2015 at 3:40 PM, Cristian Rinaldi 
>>> wrote:
>>>
 Thanks Julien!!!

 This work fine!!

 El viernes, 23 de octubre de 2015, 4:13:55 (UTC-3), Goktug Gokdogan
 escribió:
>
> As we are getting close to 2.8 release I wrote a new document that is
> concentrating on jsinterop features to be released in 2.8:
>
> https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
>
> Please share your feedback.
>
> Thanks,
>
> Goktug
>
 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/51f767f9-0afd-48fd-bef8-a9106b0d716a%40googlegroups.com
 
 .

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

>>>
>>> --
>>> 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-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtrYCKBHtp6ccqnxTq%3Dq2EK8jB-A57qqFX05U2sw6-12w%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D62mQ0iqjRBc8E8vbPTWqtE61gUcb-1qbKATt8wtrsUTw%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtTjvgcdJLojY4C4ouNzDUOBOXTF_TKjxRA8V2Azjoecw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk0jt7HDSPDX22f9LX5SLdxK8Hm9D1rzo92ac2qzoMXHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] CodeServer and Compiler broken after "Redo file watching refactor." change

['Roberto Lublinerman' via GWT Contributors]

It happens in windows with or without the flag I think. I run it with
logLevel DEBUG and -string and it was failing to find the sources for
javax.validation. But it is a real pain to setup an environment in windows
that runs our build. Elemental also fails to build.

On Tue, Nov 10, 2015 at 10:36 PM, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Also is this happening in any other configuration? Java8? windows 10?
>
> I can't reproduce it with mac or linux.
>
>
> On Tue, Nov 10, 2015 at 9:39 PM, 'Roberto Lublinerman' via GWT
> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> Could you run it with -Dgwt.watchFileChanges=false and let us know? That
>> flag should turn of the file watching logic.
>>
>> On Tue, Nov 10, 2015 at 6:39 AM, Lars <lars.gemeinha...@gmail.com> wrote:
>>
>>> After the "Redo file watching refactor." change
>>> (d746d952defbd42c81317ccbd5da0f1561b81d36) both CodeServer and Compiler are
>>> broken for my project and also for the following build in samples (see
>>> below).
>>> What went wrong?
>>> Btw. I'm using Windows7 and Java7...
>>>
>>> Buildfile: C:\Projects2\gwt-git\samples\build.xml
>>> build:
>>> -do:
>>> dynatable:
>>> check.build.type:
>>> source:
>>> [mkdir] Created dir:
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
>>>  [copy] Copying 15 files to
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
>>> [mkdir] Created dir:
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
>>>  [copy] Copying 4 files to
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
>>> serverlibs:
>>> [mkdir] Created dir:
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\lib
>>> compile:
>>> [mkdir] Created dir:
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
>>> [gwt.javac] Compiling 13 source files to
>>> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
>>> [gwt.javac] Note: Some input files use or override a deprecated API.
>>> [gwt.javac] Note: Recompile with -Xlint:deprecation for details.
>>> gwtc:
>>>  [java] Compiling module com.google.gwt.sample.dynatable.DynaTable
>>>  [java]Ignored 78 units with compilation errors in first pass.
>>>  [java] Compile with -strict or with -logLevel set to TRACE or DEBUG
>>> to see all errors.
>>>  [java]Finding entry point classes
>>>  [java]   [ERROR] Hint: Check the inheritance chain from your
>>> module; it may not be inheriting a required module or a module may not be
>>> adding its source path entries properly
>>>
>>> BUILD FAILED
>>> C:\Projects2\gwt-git\samples\build.xml:58: The following error occurred
>>> while executing this line:
>>> C:\Projects2\gwt-git\samples\build.xml:46: The following error occurred
>>> while executing this line:
>>> C:\Projects2\gwt-git\samples\build.xml:10: The following error occurred
>>> while executing this line:
>>> C:\Projects2\gwt-git\samples\common.ant.xml:143: Java returned: 1
>>>
>>> Total time: 13 seconds
>>>
>>> Buildfile: C:\Projects2\gwt-git\dev\codeserver\build.xml
>>> compile:
>>> build:
>>> demo:
>>>  [java] Turning off precompile in incremental mode.
>>>  [java] Super Dev Mode starting up
>>>  [java]workDir:
>>> C:\Users\LGEMEI~1\AppData\Local\Temp\gwt-codeserver-8211969745799431939.tmp
>>>  [java]Loading Java files in com.google.gwt.sample.hello.Hello.
>>>  [java]Ignored 80 units with compilation errors in first pass.
>>>  [java] Compile with -strict or with -logLevel set to TRACE or DEBUG
>>> to see all errors.
>>>  [java]Finding entry point classes
>>>  [java]   [ERROR] Hint: Check that the type name
>>> 'com.google.gwt.sample.hello.client.Hello' is really what you meant
>>>  [java]   [ERROR] Hint: Check that your classpath includes all
>>> required source roots
>>>
>>> BUILD FAILED
>>> C:\Projects2\gwt-git\dev\codeserver\build.xml:81: Java returned: 1
>>>
>>> Total time: 11 seconds
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group 

Re: [gwt-contrib] CodeServer and Compiler broken after "Redo file watching refactor." change

['Roberto Lublinerman' via GWT Contributors]

Could you run it with -Dgwt.watchFileChanges=false and let us know? That
flag should turn of the file watching logic.

On Tue, Nov 10, 2015 at 6:39 AM, Lars  wrote:

> After the "Redo file watching refactor." change
> (d746d952defbd42c81317ccbd5da0f1561b81d36) both CodeServer and Compiler are
> broken for my project and also for the following build in samples (see
> below).
> What went wrong?
> Btw. I'm using Windows7 and Java7...
>
> Buildfile: C:\Projects2\gwt-git\samples\build.xml
> build:
> -do:
> dynatable:
> check.build.type:
> source:
> [mkdir] Created dir:
> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
>  [copy] Copying 15 files to
> C:\Projects2\gwt-git\build\out\samples\DynaTable\src
> [mkdir] Created dir:
> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
>  [copy] Copying 4 files to
> C:\Projects2\gwt-git\build\out\samples\DynaTable\war
> serverlibs:
> [mkdir] Created dir:
> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\lib
> compile:
> [mkdir] Created dir:
> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
> [gwt.javac] Compiling 13 source files to
> C:\Projects2\gwt-git\build\out\samples\DynaTable\war\WEB-INF\classes
> [gwt.javac] Note: Some input files use or override a deprecated API.
> [gwt.javac] Note: Recompile with -Xlint:deprecation for details.
> gwtc:
>  [java] Compiling module com.google.gwt.sample.dynatable.DynaTable
>  [java]Ignored 78 units with compilation errors in first pass.
>  [java] Compile with -strict or with -logLevel set to TRACE or DEBUG
> to see all errors.
>  [java]Finding entry point classes
>  [java]   [ERROR] Hint: Check the inheritance chain from your
> module; it may not be inheriting a required module or a module may not be
> adding its source path entries properly
>
> BUILD FAILED
> C:\Projects2\gwt-git\samples\build.xml:58: The following error occurred
> while executing this line:
> C:\Projects2\gwt-git\samples\build.xml:46: The following error occurred
> while executing this line:
> C:\Projects2\gwt-git\samples\build.xml:10: The following error occurred
> while executing this line:
> C:\Projects2\gwt-git\samples\common.ant.xml:143: Java returned: 1
>
> Total time: 13 seconds
>
> Buildfile: C:\Projects2\gwt-git\dev\codeserver\build.xml
> compile:
> build:
> demo:
>  [java] Turning off precompile in incremental mode.
>  [java] Super Dev Mode starting up
>  [java]workDir:
> C:\Users\LGEMEI~1\AppData\Local\Temp\gwt-codeserver-8211969745799431939.tmp
>  [java]Loading Java files in com.google.gwt.sample.hello.Hello.
>  [java]Ignored 80 units with compilation errors in first pass.
>  [java] Compile with -strict or with -logLevel set to TRACE or DEBUG
> to see all errors.
>  [java]Finding entry point classes
>  [java]   [ERROR] Hint: Check that the type name
> 'com.google.gwt.sample.hello.client.Hello' is really what you meant
>  [java]   [ERROR] Hint: Check that your classpath includes all
> required source roots
>
> BUILD FAILED
> C:\Projects2\gwt-git\dev\codeserver\build.xml:81: Java returned: 1
>
> Total time: 11 seconds
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/e6734a71-0fe4-4cdb-b56a-ef45a690ff44%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DD%3DAKYZeRENFNRGOOZ2zir_ZL3bqMXKZE_0k0QnpraJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT compiler optimization breaks some lambdas

['Roberto Lublinerman' via GWT Contributors]

>
> I did not use pretty style because I thought that this flag produces
> different result, I tested now and looks like the output is the same, but,
> I'm pretty sure that some flags changes this issues, optimize is obvious
> that fixes the problem, but I think that namespace=package also changes the
> result.
>

In a nutshell there are optimizations on the Java AST and those are not
affected at all by -style or -Xnamespace. Optimizations that are related to
types, instantiability, devirtualization, etc, are done in the Java AST.

Some optimizations in that JavaScriptAST might be affected by -style (like
DuplicateFunctionRemoval) but those I think they are mostly off. I don't
think -Xnamespace has any impact on optimizations.

That said, if you are using JsInterop, and you have a type that is never
new'ed in Java, the compiler infers that is not instantiable and assumes it
is always null and optimizes accordingly. Types originating from JavaScript
need to be marked as JsType so that the compiler is aware and does not
assume they are null.

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmdNkvotuVz_2W6ht79ZRH-DB3ohE%3DMGvxLwRyWAxMDwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT compiler optimization breaks some lambdas

['Roberto Lublinerman' via GWT Contributors]

It would be really helpful if you could isolate your problem to a small
example.

On Mon, Oct 26, 2015 at 2:39 PM, Roberto Lublinerman <rlu...@google.com>
wrote:

> I did not use pretty style because I thought that this flag produces
>> different result, I tested now and looks like the output is the same, but,
>> I'm pretty sure that some flags changes this issues, optimize is obvious
>> that fixes the problem, but I think that namespace=package also changes the
>> result.
>>
>
> In a nutshell there are optimizations on the Java AST and those are not
> affected at all by -style or -Xnamespace. Optimizations that are related to
> types, instantiability, devirtualization, etc, are done in the Java AST.
>
> Some optimizations in that JavaScriptAST might be affected by -style (like
> DuplicateFunctionRemoval) but those I think they are mostly off. I don't
> think -Xnamespace has any impact on optimizations.
>
> That said, if you are using JsInterop, and you have a type that is never
> new'ed in Java, the compiler infers that is not instantiable and assumes it
> is always null and optimizes accordingly. Types originating from JavaScript
> need to be marked as JsType so that the compiler is aware and does not
> assume they are null.
>
>
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DO7iy7S5Sha3ZsATY-aFeckFwFH9mOuJBGMOerPqMvsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Gerrit -> Github issue linking

['Roberto Lublinerman' via GWT Contributors]

Use Bug-link, see https://gwt-review.googlesource.com/#/c/13710/

On Sun, Oct 25, 2015 at 5:25 AM, Jens  wrote:

> Hi,
>
> In Gerrit "Bug: issue " points to Google Code. Do we already have an
> alternative wording for cross linking to Github? Something like "Bug:
> #" maybe?
>
> -- J.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2a50252d-fd29-44cd-9538-45a9e7d91532%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk%2BkBkH7_RDdDOdfwQSz9_E8or2foy-r9NrmrwzwqdwVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT compiler optimization breaks some lambdas

['Roberto Lublinerman' via GWT Contributors]

Are you using a recent snapshot?
On Oct 24, 2015 04:40, "Ignacio Baca Moreno-Torres" 
wrote:

> There is a bug which optimizations nullify variables which might not be
> null. I'm trying to reproduce the error outside our app but I can't, I'll
> continue trying, but for now I going to describe the problem.
>
> return service.get().getBootstrap().bootstrap().doOnNext(data -> {
> Account account = data.getAccount();
> if (account == null) auth.get().resetSessionData(false);
> else auth.get().setSessionData(account, data.getKeychain());
> theme.get().setCustomization(data.getCustomization());
> analytics.get().init(data.getAnalyticsUserAccount() + ":" + 
> data.getAnalyticsDomainName());
> OsmQueryResolver.configureServer(data.getReverseGeocodingUrl());
> final String user = account == null ? "anonymous" : account.getEmail();
> log.fine("Bootstrap data loaded successfully (user=" + user + ")");
> });
>
> Produces the next js code.
> function fie(a) {
> var b;
> null .b1();
> bdf(Tub(a.b.Ee(), 388), false);
> Ujf((b = Tub(a.k.Ee(), 937),
> null .b1(),
> b));
> Tub(a.a.Ee(), 6122).VI(null .b1() + ':' + null .b1());
> Ivg(null .b1());
> U_l(cie, 'Bootstrap data loaded successfully (user=anonymous)')
> }
> BUT! if compile without optimizations (ex. using draft compile) or if
> anonymous class is used instead of a lambda, the output js is ok. Next
> block contains my current working code.
>
> //noinspection Convert2Lambda GWT optimize incompatible
> return service.get().getBootstrap().bootstrap().doOnNext(new 
> Action1() {
> @Override public void call(EntryPointData data) {
>
>
> The bootstrap method is a call of reactive restygwt service using this
> proyect https://github.com/ibaca/restygwt-rxadapter. I.e. bootstrap
> return an Observable which end up making a XMLHttpRequest (a lot of layer
> in between), and data is a EntryPoint interface, and the implementation
> received is an overlay.
>
> I know that with this info is almost impossible to discover the problem,
> but I put here to see if someone else have similar problem, and maybe some
> gwt compiler developer just seeing that may see where is the problem
> (improbable). If a get reproduced in a sample project I write back here.
>
> --
> 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-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/89de2084-b91d-415e-8f68-2bdb3159f702%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gn0j4oyMbkCkYGWHG2H4zgVwALGGZqQUTb%3DBjEZ4DbSiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT compiler optimization breaks some lambdas

['Roberto Lublinerman' via GWT Contributors]

The only thing I can think of is that when the class is created for the
lambda in gwtastbuilder, the super class or implemented interfaces are not
set up correctly.

I'll check later to see if that is there case.
On Oct 24, 2015 19:07, "'Ray Cromwell' via GWT Contributors" <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Are you using @JsFunction/JsInterop? Unless the implementation has changed
> recently, Lambda's are supported in GWT by essentially synthesizing static
> inner classes, and so if static inner classes work, but lambda's don't,
> it's really weird. The optimization stages no nothing of lambdas and only
> see Java classes. The exception is @JsFunction.
>
>
> On Sat, Oct 24, 2015 at 2:37 PM, Ignacio Baca Moreno-Torres <
> igna...@bacamt.com> wrote:
>
>> This was from 94e45975a06ece1b8d65541aaabf833f9d8c7b07 (6 October 2015
>> at 04:29:19 GMT+2), I'll try tomorrow with HEAD, but looking the commits
>> looks improbable that the problem has been solved.
>>
>> On Sat, Oct 24, 2015 at 10:30 PM 'Roberto Lublinerman' via GWT
>> Contributors <google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> Are you using a recent snapshot?
>>> On Oct 24, 2015 04:40, "Ignacio Baca Moreno-Torres" <igna...@bacamt.com>
>>> wrote:
>>>
>>>> There is a bug which optimizations nullify variables which might not be
>>>> null. I'm trying to reproduce the error outside our app but I can't, I'll
>>>> continue trying, but for now I going to describe the problem.
>>>>
>>>> return service.get().getBootstrap().bootstrap().doOnNext(data -> {
>>>> Account account = data.getAccount();
>>>> if (account == null) auth.get().resetSessionData(false);
>>>> else auth.get().setSessionData(account, data.getKeychain());
>>>> theme.get().setCustomization(data.getCustomization());
>>>> analytics.get().init(data.getAnalyticsUserAccount() + ":" + 
>>>> data.getAnalyticsDomainName());
>>>> OsmQueryResolver.configureServer(data.getReverseGeocodingUrl());
>>>> final String user = account == null ? "anonymous" : account.getEmail();
>>>> log.fine("Bootstrap data loaded successfully (user=" + user + ")");
>>>> });
>>>>
>>>> Produces the next js code.
>>>> function fie(a) {
>>>> var b;
>>>> null .b1();
>>>> bdf(Tub(a.b.Ee(), 388), false);
>>>> Ujf((b = Tub(a.k.Ee(), 937),
>>>> null .b1(),
>>>> b));
>>>> Tub(a.a.Ee(), 6122).VI(null .b1() + ':' + null .b1());
>>>> Ivg(null .b1());
>>>> U_l(cie, 'Bootstrap data loaded successfully (user=anonymous)')
>>>> }
>>>> BUT! if compile without optimizations (ex. using draft compile) or if
>>>> anonymous class is used instead of a lambda, the output js is ok. Next
>>>> block contains my current working code.
>>>>
>>>> //noinspection Convert2Lambda GWT optimize incompatible
>>>> return service.get().getBootstrap().bootstrap().doOnNext(new 
>>>> Action1() {
>>>> @Override public void call(EntryPointData data) {
>>>>
>>>>
>>>> The bootstrap method is a call of reactive restygwt service using this
>>>> proyect https://github.com/ibaca/restygwt-rxadapter. I.e. bootstrap
>>>> return an Observable which end up making a XMLHttpRequest (a lot of layer
>>>> in between), and data is a EntryPoint interface, and the implementation
>>>> received is an overlay.
>>>>
>>>> I know that with this info is almost impossible to discover the
>>>> problem, but I put here to see if someone else have similar problem, and
>>>> maybe some gwt compiler developer just seeing that may see where is the
>>>> problem (improbable). If a get reproduced in a sample project I write back
>>>> here.
>>>>
>>>> --
>>>> 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-contributors+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/89de2084-b91d-415e-8f68-2bdb3159f702%40googlegroups.com
>>>> <https://g

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

['Roberto Lublinerman' via GWT Contributors]

I have uploaded the real fix for review at
https://gwt-review.googlesource.com/#/c/12920.

It should fix your situation but  could you verify?

On Tue, Jun 9, 2015 at 10:08 AM, 'Chris DiGiano' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Roberto, if it's any hint to the underlying problem: you're right that
 that the class is not reference anywhere else—it is used solely for the
 purpose of type coercion.

 Chris

 On Tue, Jun 9, 2015 at 10:48 AM 'Ray Cromwell' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Chris,
   My change actually fixed a bug which may have obscured a problem. There
 were duplicate class literals being generated. So you'd get
 InterfaceFoo.class twice in the output, and it may be in SDM you'd be
 covered, but in regular compiled mode you'd get the duplicates which were
 causing closure compiler issues.

  Roberto,  Maybe this is an issue with
 ControlFlowRecorder/RapidTypeAnalyzer and interface literals?


 On Tue, Jun 9, 2015 at 9:43 AM, 'Chris DiGiano' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 @Ray, rolling back your change indeed fixed the problem (
 https://gwt-review.googlesource.com/#/c/12311/). How do you recommend
 we proceed? Anything I can do to help?

 @Roberto, thanks for your suggestion, but I had already tried restarting
 the code server and clearing the cache. This did not fix things.

 Chris

 On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT
 Contributors google-web-toolkit-contributors@googlegroups.com wrote:

 This might be due to the way we handle class literals. Class literals
 for interfaces if not referenced during the initial compile might cause
 that error. The error should go aways if you restart SDM.

 The offending sequence is

 0) Suppose initially you have (interface A, class B and class C) and
 start SDM.
 1) Now edit class B to add a reference to A.class and recompile with
 SDM (do not touch A at this time nor anything that makes it recompile) .
 This should work fine because the literals that are referenced but whose
 classes where not part of this compile will be generated in the epilogue.
 2) Now edit class C in any way that does not make B or A recompile.
 Here you will have an error like the one you described.

 If you restart SDM at this point it should work.

 I'll get a fix for this tomorrow.




 On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Ooops, wrong pointer (for external users) This one
 https://gwt-review.googlesource.com/#/c/12311/


 On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
 wrote:

 Try rolling back this CL and see if it fixes it (
 https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
 )


 On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com
 wrote:

 I'm having trouble referencing a JsType interface when running under
 superdevmode. I'm trying to pass the JsType as a class reference to a
 method that uses the class to coerce the results into the expected type:

 myelement.getCustomStampedElement(dialog,
 PolymerDialog.class).open();

 Unfortunately, in superdevmode (and only in SDM) I get this error:

 Uncaught ReferenceError:
 Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
 is not defined

 PolymerDialog is declared like this:

 @JsType
 public interface PolymerDialog {
   void open();
 }

 and getCustomStampedElement is defined like this:

 /**
  * Returns the element specified in this custom element's
 template that matches the given id
  * with the result coerced to a non-vanilla element type.
 Equivalent to Polymer's $ function.
  *
  * @see
  * a href=
 https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding
 
  * Polymer automatic node finding/a
  */
 T T getCustomStampedElement(String id, ClassT type);

 It appears that the PolymerDialog JsType is being left out of the
 list of class literals available in superdevmode. Is this a bug? Any 
 ideas
 for workarounds?

 Chris DiGiano

  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.



  --
 You received this message because you are subscribed

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

['Roberto Lublinerman' via GWT Contributors]

SDM expects that classes/interfaces get generated as a whole either all of
it or none. As you know, class literals are not really part of the class
but they are field in a separate synthetic class). Even SDM (with all
optimizations off, no pruning at UnifyAST) if a reference to the class
literal is not seen when generating the JS for the class then its class
literal field wont be part of the JS for the class.

For SDM it could only happen for interfaces (and maybe primitive types)
because GwtAstBuilder will synthezise a getClass for each class containing
reference to its class literals.

The problem is further obscured because we (re)generate an epilogue each
time and it contains all the class literals that are referenced from the
code that is being recompiled whose classes where not part of the current
compile. This serves a purpose in NON SDM where if only the class literal
for a class is referenced, the class can be pruned.

The only glitch remaining is that in SDM there might be duplicated class
literals (but it should not affect the correctness). Is this an issue for
Closure?

On Tue, Jun 9, 2015 at 9:48 AM, 'Ray Cromwell' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Chris,
   My change actually fixed a bug which may have obscured a problem. There
 were duplicate class literals being generated. So you'd get
 InterfaceFoo.class twice in the output, and it may be in SDM you'd be
 covered, but in regular compiled mode you'd get the duplicates which were
 causing closure compiler issues.

  Roberto,  Maybe this is an issue with
 ControlFlowRecorder/RapidTypeAnalyzer and interface literals?


 On Tue, Jun 9, 2015 at 9:43 AM, 'Chris DiGiano' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 @Ray, rolling back your change indeed fixed the problem (
 https://gwt-review.googlesource.com/#/c/12311/). How do you recommend we
 proceed? Anything I can do to help?

 @Roberto, thanks for your suggestion, but I had already tried restarting
 the code server and clearing the cache. This did not fix things.

 Chris

 On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT Contributors
 google-web-toolkit-contributors@googlegroups.com wrote:

 This might be due to the way we handle class literals. Class literals
 for interfaces if not referenced during the initial compile might cause
 that error. The error should go aways if you restart SDM.

 The offending sequence is

 0) Suppose initially you have (interface A, class B and class C) and
 start SDM.
 1) Now edit class B to add a reference to A.class and recompile with SDM
 (do not touch A at this time nor anything that makes it recompile) . This
 should work fine because the literals that are referenced but whose classes
 where not part of this compile will be generated in the epilogue.
 2) Now edit class C in any way that does not make B or A recompile. Here
 you will have an error like the one you described.

 If you restart SDM at this point it should work.

 I'll get a fix for this tomorrow.




 On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Ooops, wrong pointer (for external users) This one
 https://gwt-review.googlesource.com/#/c/12311/


 On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
 wrote:

 Try rolling back this CL and see if it fixes it (
 https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
 )


 On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com wrote:

 I'm having trouble referencing a JsType interface when running under
 superdevmode. I'm trying to pass the JsType as a class reference to a
 method that uses the class to coerce the results into the expected type:

 myelement.getCustomStampedElement(dialog,
 PolymerDialog.class).open();

 Unfortunately, in superdevmode (and only in SDM) I get this error:

 Uncaught ReferenceError:
 Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
 is not defined

 PolymerDialog is declared like this:

 @JsType
 public interface PolymerDialog {
   void open();
 }

 and getCustomStampedElement is defined like this:

 /**
  * Returns the element specified in this custom element's
 template that matches the given id
  * with the result coerced to a non-vanilla element type.
 Equivalent to Polymer's $ function.
  *
  * @see
  * a href=
 https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding
 
  * Polymer automatic node finding/a
  */
 T T getCustomStampedElement(String id, ClassT type);

 It appears that the PolymerDialog JsType is being left out of the
 list of class literals available in superdevmode. Is this a bug? Any 
 ideas
 for workarounds?

 Chris DiGiano

  --
 You received this message because you are subscribed

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

['Roberto Lublinerman' via GWT Contributors]

I tweaked the code a bit and now it should never output duplicated class
literals. @Ray, Could you review the patch?

On Tue, Jun 9, 2015 at 10:31 AM, 'Ray Cromwell' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I don't think it's an issue that blocks since people are most likely to
 use SDM in uncompiled mode, and the 'error' can always be suppressed and
 turned into a warning. At best, it might inhibit a const optimization in
 Closure where it sees the same variable declared/assigned twice I think.


 On Tue, Jun 9, 2015 at 10:27 AM, 'Roberto Lublinerman' via GWT
 Contributors google-web-toolkit-contributors@googlegroups.com wrote:

 SDM expects that classes/interfaces get generated as a whole either all
 of it or none. As you know, class literals are not really part of the class
 but they are field in a separate synthetic class). Even SDM (with all
 optimizations off, no pruning at UnifyAST) if a reference to the class
 literal is not seen when generating the JS for the class then its class
 literal field wont be part of the JS for the class.

 For SDM it could only happen for interfaces (and maybe primitive types)
 because GwtAstBuilder will synthezise a getClass for each class containing
 reference to its class literals.

 The problem is further obscured because we (re)generate an epilogue each
 time and it contains all the class literals that are referenced from the
 code that is being recompiled whose classes where not part of the current
 compile. This serves a purpose in NON SDM where if only the class literal
 for a class is referenced, the class can be pruned.

 The only glitch remaining is that in SDM there might be duplicated class
 literals (but it should not affect the correctness). Is this an issue for
 Closure?

 On Tue, Jun 9, 2015 at 9:48 AM, 'Ray Cromwell' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Chris,
   My change actually fixed a bug which may have obscured a problem.
 There were duplicate class literals being generated. So you'd get
 InterfaceFoo.class twice in the output, and it may be in SDM you'd be
 covered, but in regular compiled mode you'd get the duplicates which were
 causing closure compiler issues.

  Roberto,  Maybe this is an issue with
 ControlFlowRecorder/RapidTypeAnalyzer and interface literals?


 On Tue, Jun 9, 2015 at 9:43 AM, 'Chris DiGiano' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 @Ray, rolling back your change indeed fixed the problem (
 https://gwt-review.googlesource.com/#/c/12311/). How do you recommend
 we proceed? Anything I can do to help?

 @Roberto, thanks for your suggestion, but I had already tried
 restarting the code server and clearing the cache. This did not fix things.

 Chris

 On Mon, Jun 8, 2015 at 6:55 PM 'Roberto Lublinerman' via GWT
 Contributors google-web-toolkit-contributors@googlegroups.com wrote:

 This might be due to the way we handle class literals. Class literals
 for interfaces if not referenced during the initial compile might cause
 that error. The error should go aways if you restart SDM.

 The offending sequence is

 0) Suppose initially you have (interface A, class B and class C) and
 start SDM.
 1) Now edit class B to add a reference to A.class and recompile with
 SDM (do not touch A at this time nor anything that makes it recompile) .
 This should work fine because the literals that are referenced but whose
 classes where not part of this compile will be generated in the epilogue.
 2) Now edit class C in any way that does not make B or A recompile.
 Here you will have an error like the one you described.

 If you restart SDM at this point it should work.

 I'll get a fix for this tomorrow.




 On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors 
 google-web-toolkit-contributors@googlegroups.com wrote:

 Ooops, wrong pointer (for external users) This one
 https://gwt-review.googlesource.com/#/c/12311/


 On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
 wrote:

 Try rolling back this CL and see if it fixes it (
 https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
 )


 On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com
 wrote:

 I'm having trouble referencing a JsType interface when running
 under superdevmode. I'm trying to pass the JsType as a class reference 
 to a
 method that uses the class to coerce the results into the expected 
 type:

 myelement.getCustomStampedElement(dialog,
 PolymerDialog.class).open();

 Unfortunately, in superdevmode (and only in SDM) I get this error:

 Uncaught ReferenceError:
 Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
 is not defined

 PolymerDialog is declared like this:

 @JsType
 public interface PolymerDialog {
   void open();
 }

 and getCustomStampedElement

Re: [gwt-contrib] Class literals for JsTypes in superdevmode

['Roberto Lublinerman' via GWT Contributors]

This might be due to the way we handle class literals. Class literals for
interfaces if not referenced during the initial compile might cause that
error. The error should go aways if you restart SDM.

The offending sequence is

0) Suppose initially you have (interface A, class B and class C) and start
SDM.
1) Now edit class B to add a reference to A.class and recompile with SDM
(do not touch A at this time nor anything that makes it recompile) . This
should work fine because the literals that are referenced but whose classes
where not part of this compile will be generated in the epilogue.
2) Now edit class C in any way that does not make B or A recompile. Here
you will have an error like the one you described.

If you restart SDM at this point it should work.

I'll get a fix for this tomorrow.




On Mon, Jun 8, 2015 at 3:23 PM, 'Ray Cromwell' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Ooops, wrong pointer (for external users) This one
 https://gwt-review.googlesource.com/#/c/12311/


 On Mon, Jun 8, 2015 at 3:14 PM, Ray Cromwell cromwell...@google.com
 wrote:

 Try rolling back this CL and see if it fixes it (
 https://critique.corp.google.com/#review/92873682/depot/google3/third_party/java_src/gwt/svn/trunk/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
 )


 On Mon, Jun 8, 2015 at 3:04 PM, Chris DiGiano d...@google.com wrote:

 I'm having trouble referencing a JsType interface when running under
 superdevmode. I'm trying to pass the JsType as a class reference to a
 method that uses the class to coerce the results into the expected type:

 myelement.getCustomStampedElement(dialog,
 PolymerDialog.class).open();

 Unfortunately, in superdevmode (and only in SDM) I get this error:

 Uncaught ReferenceError:
 Lcom_google_ccc_groups_rosters_frontend_polymer_jstype_PolymerDialog_2_classLit_0_g$
 is not defined

 PolymerDialog is declared like this:

 @JsType
 public interface PolymerDialog {
   void open();
 }

 and getCustomStampedElement is defined like this:

 /**
  * Returns the element specified in this custom element's template
 that matches the given id
  * with the result coerced to a non-vanilla element type. Equivalent
 to Polymer's $ function.
  *
  * @see
  * a href=
 https://www.polymer-project.org/1.0/docs/devguide/local-dom.html#node-finding
 
  * Polymer automatic node finding/a
  */
 T T getCustomStampedElement(String id, ClassT type);

 It appears that the PolymerDialog JsType is being left out of the list
 of class literals available in superdevmode. Is this a bug? Any ideas for
 workarounds?

 Chris DiGiano

  --
 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-contributors+unsubscr...@googlegroups.com
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/9826758e-1b0f-4797-8902-738a1fade037%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.



  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7fZhv0AkiPYqfM2WWaW8zFvdgk-BYEucwRP8k4ewXEp6w%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7fZhv0AkiPYqfM2WWaW8zFvdgk-BYEucwRP8k4ewXEp6w%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk_U85%2B6z1QK9XpAKEXbBJgviBfZ1j0kgE8_pYZsV6Y3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot

['Roberto Lublinerman' via GWT Contributors]

Balázs, the js.embedded.properties configuration property might help here.

Try adding

extend-configuration-property name=js.embedded.properties
value=my.platform /


to your gwt.xml file


On Tue, May 5, 2015 at 6:26 AM, Kishore Palakollu 
kishorepalako...@gmail.com wrote:

 Hi Robert,
  i m facing the same issue. can you please tell me what has fixed
 your issue.

 My compilation-mappings.txt contains

 B5079040E7FF0E555046C1AD8B647A66.cache.js
 locale en_EN
 user.agent gecko1_8

 B5079040E7FF0E555046C1AD8B647A66.cache.js
 locale en_EN
 user.agent ie10

 B5079040E7FF0E555046C1AD8B647A66.cache.js
 locale en_EN
 user.agent ie9

 B5079040E7FF0E555046C1AD8B647A66.cache.js
 locale en_EN
 user.agent safari

 Devmode:devmode.js

 Thanks  Regards,
 kishore.

 On Thursday, 4 December 2014 19:24:48 UTC+5:30, Robert Hoffmann wrote:

  @thomas

 thank you, that helped me to reduce the permutations to one.

 For the record, compilation-mappings.txt contained multiple cache.js file
 entries, now it only contains one
 
 FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js

 Devmode:devmode.js
 
 ...and now sdm works.

 And it's fast :-)


 On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote:

 Hi,

  Is there a way to see which properties cause the permutations?
 (I'm using GWT 2.7.0)


  When compiling your project, you should have a compilation-mappings.txt
 file generated next to the *.nocache.js.

   --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/bcf4a9ce-75f7-40af-a8c0-05273db066ee%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/bcf4a9ce-75f7-40af-a8c0-05273db066ee%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DgxjSsQ8moFkszusQE_oNdT4yLwGBqdSyiYJGpM96Jcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] status of lambdas

['Roberto Lublinerman' via GWT Contributors]

Lambdas work fine in master.

On Fri, Apr 24, 2015 at 6:02 PM, Stephen Haberman 
stephen.haber...@gmail.com wrote:

 Just curious, but what is the state of lambdas on master?
 Probably works? Known broken in some hairy boundary cases? Being
 used in production?

 Thanks,
 Stephen

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/20150424200256.684f2d7d%40sh9
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmqgjXv33_mS%2BosPfXtaYUDVNiA5zvtfgSFSz-9pWS6ww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Jsni on String methods in GWT 2.7

['Roberto Lublinerman' via GWT Contributors]

Please file an issue to keep track.

On Mon, Mar 30, 2015 at 9:06 AM, Roberto Lublinerman rlu...@google.com
wrote:

 GWT strings and arrays are JS native strings and arrays (no prototype
 monkey patching), in Java code calls to Object, String, Array and
 Comparable methods are devirtualized if applied to instances typed at one
 of those types.

 So the answer is yes: You wont be able to call instance methods this way
 for strings and arrays. At least, we should emit an error if you try to get
 a JSNI reference to a String or array method, and probably a warning if you
 make a jsni reference to a Object or Comparable method. Getting a jsni
 reference to Object or Comparable method works fine on every object as long
 as it is not a String or Array.


 On Sun, Mar 29, 2015 at 5:42 PM, James Nelson ja...@wetheinter.net
 wrote:

 I'm not sure if this is intended, but I've noticed that JSNI methods on
 string do not work.
 I tried equals, compareTo, compareToIgnoreCase and charAt, but none of
 them worked.
 I used my fork and the pristine 2.7, and in super dev + regular compile;
 in all cases, the functions come back undefined.

 native char jsni(String s)
 /*-{
   var fn = s...@java.lang.String::charAt(I);
   // fn is undefined
   return fn(0); // doom
 }-*/;

 In compiled code, it looks something like:
 var fn = string_0_g$.charAt_3_g$;


 So, my question, is this expected behaviour?

 If so, are there other types I need to guard against JSNI failures?

 If not, should I file a bug and look into a patch?
 (Assuming a patch would be a rewrite static method visitor that can
 replace jsni method refs with a staticified version).

 For my reflection support, I'm going to guard against this by making
 public methods not use JSNI,
 but if there are other types or gotchas I should be aware of, it would be
 nice to know about them.


 Thanks!

  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/996e0a45-0048-4a61-abdd-3bff209df09d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/996e0a45-0048-4a61-abdd-3bff209df09d%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DAH1hEa8GbirmOfgiK%2BfYWbEi_oCJ5SD7CwJZNkR%2Bm8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Jsni on String methods in GWT 2.7

['Roberto Lublinerman' via GWT Contributors]

GWT strings and arrays are JS native strings and arrays (no prototype
monkey patching), in Java code calls to Object, String, Array and
Comparable methods are devirtualized if applied to instances typed at one
of those types.

So the answer is yes: You wont be able to call instance methods this way
for strings and arrays. At least, we should emit an error if you try to get
a JSNI reference to a String or array method, and probably a warning if you
make a jsni reference to a Object or Comparable method. Getting a jsni
reference to Object or Comparable method works fine on every object as long
as it is not a String or Array.


On Sun, Mar 29, 2015 at 5:42 PM, James Nelson ja...@wetheinter.net wrote:

 I'm not sure if this is intended, but I've noticed that JSNI methods on
 string do not work.
 I tried equals, compareTo, compareToIgnoreCase and charAt, but none of
 them worked.
 I used my fork and the pristine 2.7, and in super dev + regular compile;
 in all cases, the functions come back undefined.

 native char jsni(String s)
 /*-{
   var fn = s...@java.lang.String::charAt(I);
   // fn is undefined
   return fn(0); // doom
 }-*/;

 In compiled code, it looks something like:
 var fn = string_0_g$.charAt_3_g$;


 So, my question, is this expected behaviour?

 If so, are there other types I need to guard against JSNI failures?

 If not, should I file a bug and look into a patch?
 (Assuming a patch would be a rewrite static method visitor that can
 replace jsni method refs with a staticified version).

 For my reflection support, I'm going to guard against this by making
 public methods not use JSNI,
 but if there are other types or gotchas I should be aware of, it would be
 nice to know about them.


 Thanks!

  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/996e0a45-0048-4a61-abdd-3bff209df09d%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/996e0a45-0048-4a61-abdd-3bff209df09d%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3D1RED4t2_ZJN9skhPM85UzkTBks-Xo3MAtsvqJ%2BrJruw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Snapshot repo?

['Roberto Lublinerman' via GWT Contributors]

Build is green now. I am not sure about sonatype, let's wait for dankurka
to chime in...

On Wed, Mar 25, 2015 at 9:30 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

 Couldn't we configure sonatype to keep at least the last snapshot even if
 we don't update the repository (because the build failed)  ?


 On Thu, Mar 19, 2015 at 5:45 PM 'Roberto Lublinerman' via GWT Contributors
 google-web-toolkit-contributors@googlegroups.com wrote:

 We are looking into it and will be hopefully resolved soon.

 On Thu, Mar 19, 2015 at 8:15 AM, Colin Alworth niloc...@gmail.com
 wrote:

 It looks like the build is failing, and has been for some days:
 http://build.gwtproject.org/job/gwt/49/#showFailuresLink

 Test Result (26 failures / -6)

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_bridgeMethodOverrideChain

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsCascadedGenerators
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dateStampChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatePreamble
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superClassOrder

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superFromStaleInner

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_deterministicUiBinder

 com.google.gwt.dev.CompilerTest.testDeterministicBuild_Draft_StackModeStrip

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_uiBinderCssChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unstableGeneratorReferencesModifiedType

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_functionSignatureChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_compileTimeConstantChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_transitivelyFoldableConstant

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_packagePrivateDispatch

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_regularClassMadeIntoJsoClass

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unreachableIncompatibleChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_typeHierarchyChange
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_defaultMethod

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeUnchangedJso

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeString

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_multipleClassGenerator

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_singleJsoIntfDispatchChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dualJsoIntfDispatchChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_generatorInputResourceChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsGenerator

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_carriesOverGeneratorArtifacts


 On Thursday, March 19, 2015 at 8:04:34 AM UTC-5, Ali Akhtar wrote:

 Hey guys,

 Is there a maven repo to use for getting snapshot builds? Sonatype
 doesn't contain .jars,

 https://oss.sonatype.org/content/repositories/google-
 snapshots/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/

 And https://github.com/manolo/gwt-snapshot/ doesn't appear to have
 been updated for 28 days.

 Thanks.

  --
 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-contributors+unsubscr...@googlegroups.com
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad62891f-a1f0-4c59-ac18-7c6b877f2088%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad62891f-a1f0-4c59-ac18-7c6b877f2088%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk%3DDo5V1vK0wcEZX0Gu2386NiGcax-XTTFDtMWgR5z93g%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk%3DDo5V1vK0wcEZX0Gu2386NiGcax-XTTFDtMWgR5z93g%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.

  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors

Re: [gwt-contrib] Java8 emulation

['Roberto Lublinerman' via GWT Contributors]

I think we make run presubmits with Java 8. AFAIK presubmit only build the
compiler (to see that is buildable) and run checkstyle. We will still run
our main continuous build in Java 7 and there is an alternate continuous
build with Java 8 (which is now broken).

Can someone look at those failures? Internally apart from the 2 failing tck
tests (which we could disable until we upgrade validation) all the others
are passing.

I am not sure why
On Wed, Mar 25, 2015 at 8:38 AM, John A. Tamplin j...@jaet.org wrote:

 On Wed, Mar 25, 2015 at 11:33 AM, Colin Alworth niloc...@gmail.com
 wrote:

 The trick seems to be that it is not going to be possible to add Java8
 emul code without actually using Java8 - while lambdas can be avoided,
 defender methods cannot. If you need to provide a new interface like
 Consumer, the supersource *must* have the `default` method(s), or it won't
 actually be Consumer.

 If it were just those types, it would be possible to move them into their
 own module so developers would need to inherit's the Java8 module to get
 access to them, but the Collection interface itself needs to be changed to
 add `default StreamE stream()`, plus the implementation, or else all
 implementors of Collection (and Set and List) need to have an
 implementation added. Even then, Stream would need to be emulated, which
 references Consumer, so we can't have it be a separate module...

 ...or am I over-complicating matters?


 Well, certainly there are things which will require further support in GWT
 and in the build, but things like adding j.u.Optional can be done without
 that.

 --
 John A. Tamplin

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM5k6X_k%2BwvoH_a_YquYcxY-uzbL%3DdANNn5eGZZJUombafbKBA%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM5k6X_k%2BwvoH_a_YquYcxY-uzbL%3DdANNn5eGZZJUombafbKBA%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkfKK09OCGwME0t_VBmXNcSJFKSTF1%3DPAA3gWsgzAo7Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Snapshot repo?

['Roberto Lublinerman' via GWT Contributors]

We are looking into it and will be hopefully resolved soon.

On Thu, Mar 19, 2015 at 8:15 AM, Colin Alworth niloc...@gmail.com wrote:

 It looks like the build is failing, and has been for some days:
 http://build.gwtproject.org/job/gwt/49/#showFailuresLink

 Test Result (26 failures / -6)

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_bridgeMethodOverrideChain

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsCascadedGenerators
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dateStampChange
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatePreamble
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superClassOrder

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_superFromStaleInner

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_deterministicUiBinder
 com.google.gwt.dev.CompilerTest.testDeterministicBuild_Draft_StackModeStrip
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_uiBinderCssChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unstableGeneratorReferencesModifiedType

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_functionSignatureChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_compileTimeConstantChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_transitivelyFoldableConstant

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_packagePrivateDispatch

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_regularClassMadeIntoJsoClass

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_unreachableIncompatibleChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_typeHierarchyChange
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_defaultMethod

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeUnchangedJso
 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_devirtualizeString

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_multipleClassGenerator

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_singleJsoIntfDispatchChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_dualJsoIntfDispatchChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_generatorInputResourceChange

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_invalidatedGeneratorOutputRerunsGenerator

 com.google.gwt.dev.CompilerTest.testIncrementalRecompile_carriesOverGeneratorArtifacts


 On Thursday, March 19, 2015 at 8:04:34 AM UTC-5, Ali Akhtar wrote:

 Hey guys,

 Is there a maven repo to use for getting snapshot builds? Sonatype
 doesn't contain .jars,

 https://oss.sonatype.org/content/repositories/google-
 snapshots/com/google/gwt/gwt-user/2.8.0-SNAPSHOT/

 And https://github.com/manolo/gwt-snapshot/ doesn't appear to have been
 updated for 28 days.

 Thanks.

  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad62891f-a1f0-4c59-ac18-7c6b877f2088%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/ad62891f-a1f0-4c59-ac18-7c6b877f2088%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk%3DDo5V1vK0wcEZX0Gu2386NiGcax-XTTFDtMWgR5z93g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8 SnapShot Unexpected internal compiler error in SDM after switching to GSS

['Roberto Lublinerman' via GWT Contributors]

Can you provide a small repro case and open an issue for it?

On Wed, Mar 18, 2015 at 6:15 AM, Travis Schmidt travis.schm...@gmail.com
wrote:

 I hit a similar problem.  I Turned on GSS with GWT 2.7 Release.  I
 converted one of my files to .gss and let the converter handle the other
 files for now.  Everything compiles fine.   Super Dev Mode will start and
 the first compile will work fine.  If I make a change the next incremental
 compile fails with the UnableToTomplete exception, with it outputting code
 that applied styles in the gss.  I turned gss off and reverted that file
 back to css and the incremental compile started working again.

 Travis


 On Friday, January 30, 2015 at 5:09:30 PM UTC-6, confile wrote:

 I use GWT 2.8 SnapShot with an app that runs with CSS only no GSS. Then I
 switched to GSS using:

 set-configuration-property name=CssResource.enableGss value=true /

  set-configuration-property name=CssResource.legacy value=true /

 set-configuration-property name=CssResource.conversionMode value=
 lenient /


 When I compile with option -strict there are no errors. When I run my
 server in SDM and try to connect I get the following errors:


  Compiling 1 permutation

 Compiling permutation 0...

 [ERROR] Unexpected internal compiler error

 java.lang.NullPointerException

 at com.google.gwt.dev.jjs.ast.HasName$1.compare(HasName.java:33)

 at com.google.gwt.dev.jjs.ast.HasName$1.compare(HasName.java:30)

 at java.util.TimSort.countRunAndMakeAscending(TimSort.java:324)

 at java.util.TimSort.sort(TimSort.java:189)

 at java.util.TimSort.sort(TimSort.java:173)

 at java.util.Arrays.sort(Arrays.java:659)

 at java.util.Collections.sort(Collections.java:217)

 at com.google.gwt.dev.jjs.ast.JTypeOracle.getCastableDestinationTypes(
 JTypeOracle.java:1019)

 at com.google.gwt.dev.jjs.impl.ComputeExhaustiveCastabilityInformation.
 createCompleteCastMap(ComputeExhaustiveCastabilityInformation.java:44)

 at com.google.gwt.dev.jjs.impl.ComputeExhaustiveCastabilityIn
 formation.execImpl(ComputeExhaustiveCastabilityInformation.java:50)

 at com.google.gwt.dev.jjs.impl.ComputeExhaustiveCastabilityIn
 formation.exec(ComputeExhaustiveCastabilityInformation.java:32)

 at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler$
 MonolithicPermutationCompiler.normalizeSemantics(
 MonolithicJavaToJavaScriptCompiler.java:102)

 at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$PermutationCompiler.
 compilePermutation(JavaToJavaScriptCompiler.java:286)

 at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptComp
 iler.compilePermutation(MonolithicJavaToJavaScriptCompiler.java:292)

 at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(
 UnifiedAst.java:130)

 at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:197)

 at com.google.gwt.dev.ThreadedPermutationWorkerFacto
 ry$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFacto
 ry.java:50)

 at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(
 PermutationWorkerFactory.java:74)

 at java.lang.Thread.run(Thread.java:745)

 [ERROR] Unrecoverable exception, shutting down

 com.google.gwt.core.ext.UnableToCompleteException: (see previous log
 entries)

 at com.google.gwt.dev.javac.CompilationProblemReporter.
 logAndTranslateException(CompilationProblemReporter.java:112)

 at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$PermutationCompiler.
 compilePermutation(JavaToJavaScriptCompiler.java:363)

 at com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptComp
 iler.compilePermutation(MonolithicJavaToJavaScriptCompiler.java:292)

 at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(
 UnifiedAst.java:130)

 at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:197)

 at com.google.gwt.dev.ThreadedPermutationWorkerFacto
 ry$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFacto
 ry.java:50)

 at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(
 PermutationWorkerFactory.java:74)

 at java.lang.Thread.run(Thread.java:745)

 [ERROR] Not all permutation were compiled , completed (0/1)

   [WARN] recompile failed

   [WARN] continuing to serve previous version


  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/13197114-92e6-475b-a6e7-974428f6cbf9%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/13197114-92e6-475b-a6e7-974428f6cbf9%40googlegroups.com?utm_medium=emailutm_source=footer
 .

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


-- 
You received this message because you are subscribed to the Google Groups GWT 
Contributors group.
To unsubscribe from this group and 

Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

['Roberto Lublinerman' via GWT Contributors]

In draft compile Java compile time constants are emitted in the prototype.
This should be exactly static final fields of primitive or string type
assigned at declaration.

This is the approach to compile time constants taken to implement Java
semantics.

FWIW in optimized compiles other fields might be upgraded to compile time
constants.
On Dec 5, 2014 2:18 AM, stuckagain david.no...@gmail.com wrote:

 I've been trying out GWT 2.7 and SuperDevMode in combination with the SDBG
 https://github.com/sdbg/sdbg eclipse plugin.

 In the Chrome debugger I noticed that some fields are sometimes available
 under 'this' but sometimes they are available only in 'this.__proto__'.
 It seems that if I have a boolean field that is set to false that it does
 not appear in 'this' but under 'this.__proto__' and that I can not see it
 at all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to
 figure out how this works in GWT SuperDevMode.

 Another thing that takes getting used: list/map structures are not that
 easy to navigate anymore. I hope they found some way to make it easier to
 have some support to convert them to something readable in the debugger.


  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] SuperDevMode sometimes puts member fields in __proto__ why is that ?

['Roberto Lublinerman' via GWT Contributors]

Yes,I meant (instance) final fields of primitive or string type initialized
at declaration.

Compile time constants are propagated by the compiler in draft and
optimized mode.



On Fri, Dec 5, 2014 at 8:49 AM, 'Ray Cromwell' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Static final fields on the prototype? I'm pretty sure these are
 promoted to global in optimized mode. Perhaps you meant final
 non-static fields? (which we should have an optimization for promoting
 to static :) )


 On Fri, Dec 5, 2014 at 7:29 AM, 'Roberto Lublinerman' via GWT
 Contributors google-web-toolkit-contributors@googlegroups.com wrote:
  In draft compile Java compile time constants are emitted in the
 prototype.
  This should be exactly static final fields of primitive or string type
  assigned at declaration.
 
  This is the approach to compile time constants taken to implement Java
  semantics.
 
  FWIW in optimized compiles other fields might be upgraded to compile
 time
  constants.
 
  On Dec 5, 2014 2:18 AM, stuckagain david.no...@gmail.com wrote:
 
  I've been trying out GWT 2.7 and SuperDevMode in combination with the
 SDBG
  eclipse plugin.
 
  In the Chrome debugger I noticed that some fields are sometimes
 available
  under 'this' but sometimes they are available only in 'this.__proto__'.
  It seems that if I have a boolean field that is set to false that it
 does
  not appear in 'this' but under 'this.__proto__' and that I can not see
 it at
  all in the SDBG plugin. I filed a bug report on SDBG, but I am trying to
  figure out how this works in GWT SuperDevMode.
 
  Another thing that takes getting used: list/map structures are not that
  easy to navigate anymore. I hope they found some way to make it easier
 to
  have some support to convert them to something readable in the debugger.
 
 
  --
  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-contributors+unsubscr...@googlegroups.com.
  To view this discussion on the web visit
 
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/d948f131-0da7-4e9a-998a-925e68a62ced%40googlegroups.com
 .
  For more options, visit https://groups.google.com/d/optout.
 
  --
  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-contributors+unsubscr...@googlegroups.com.
  To view this discussion on the web visit
 
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnmswu4mF_7SRPnZjQYjvykkTvgnnthPDfuFy5gpGamcQ%40mail.gmail.com
 .
 
  For more options, visit https://groups.google.com/d/optout.

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAPVRV7eTkVStPGXrtfiPk5kO8yr2gyjQCZY4xkAD5ufExWB_6g%40mail.gmail.com
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnaifVU5UEa7mU41UuRcEZvwp-NWv_6v5pHsq4Na%3D8uuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Not able to run any GWTTestCase

['Roberto Lublinerman' via GWT Contributors]

This looks awfully a class path issue. Did you ant clean before building?

On Fri, Nov 14, 2014 at 3:06 AM, Julien Dramaix julien.dram...@gmail.com
wrote:

 I've updated my master branch (of the GWT-core project) the with the
 remote and now I'm not able to run any GWT test cases included in the
 project. I receive first this error:


 java.lang.NoSuchFieldError: VOID
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.isGetter(JSORestrictionsChecker.java:294)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsTypeMethodsForOverloads(JSORestrictionsChecker.java:341)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkJsType(JSORestrictionsChecker.java:262)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.checkType(JSORestrictionsChecker.java:368)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker$JSORestrictionsVisitor.visit(JSORestrictionsChecker.java:239)
 at
 org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1286)
 at
 org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:712)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:601)
 at
 com.google.gwt.dev.javac.JSORestrictionsChecker.check(JSORestrictionsChecker.java:524)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater$UnitProcessorImpl.process(CompilationStateBuilder.java:99)
 at
 com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:384)
 at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470)
 at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:985)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:339)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:580)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:513)
 at
 com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:499)
 at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:668)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1312)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 Then each test case fails with:
 java.lang.NullPointerException
 at
 com.google.gwt.junit.JUnitShell.checkTestClassInCurrentModule(JUnitShell.java:714)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1321)
 at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1277)
 at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:671)
 at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)
 at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)
 at
 org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
 at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
 at
 com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:74)
 at
 com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
 at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)


 I'm sure something is wrong locally but I don't see what. Any hint ?

 Julien

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D66%3DKJkw6JW%3D4Lyk%2BPNkD6z_PMyqQp2zW%3D9ggVTjoVDrA%40mail.gmail.com
 

Re: [gwt-contrib] 2.7RC1 compiles fine but recompile returns errors

['Roberto Lublinerman' via GWT Contributors]

The reason why your are seeing error (1)  in 2.7 and not in 2.6 (I assume)
is that to implement minimal (class level) recompiles all the methods of a
class are traversed in 2.7 where only entry point reachable methods were
traversed in 2.6. In the past if you had a class that, for example,
provided constants and those were the only members really used by this
project, such a class would compile even if one of its methods referred to
a class that is not emulated.

On Fri, Nov 7, 2014 at 9:22 AM, Koen Maes k...@koma.be wrote:

 Hi

 I am trying my project with 2.7RC1. I can compile the whole project
 without errors.

 But when I start the application, recompile is triggered and this gives me
 two different errors :

 1)  java.util.StringTokenizer is not found
  Tracing compile failure path for type
 'com.klawt.shared.domain.SearchFieldsTokenizer'
 [ERROR] Errors in
 'file:/home/koen/workspace/klawt/shared/com/klawt/shared/domain/SearchFieldsTokenizer.java'
[ERROR] Line 16: No source code is available for type
 java.util.StringTokenizer; did you forget to inherit a required module?

 2) Troubles with GSS/CSS resource

  Computing all possible rebind results for
 'com.klawt.screen.ui.Resources'
 Rebinding com.klawt.screen.ui.Resources
Invoking generator
 com.google.gwt.resources.rebind.context.InlineClientBundleGenerator
   Preparing method base_admin
  The following problems were detected
 [WARN] Line 75 column 54: encountered *. Was
 expecting one of: |= ~= = ]
  [ERROR] Errors in
 'gen/com/klawt/screen/ui/menu/InvoiceMenuViewImpl_InvoiceMenuUiBinderImpl.java'
 [ERROR] Line 108: Rebind result
 'com.klawt.screen.ui.BaseAdminCssResource' must be a class

 The class BaseAdminCssResource is a CSSResource.

 public interface BaseAdminCssResource extends CssResource {

 @ClassName(widget)
 String widget();

 @ClassName(widget-header)
 String widgetHeader();

 and so on
 }


 Anybody to give me some hints what is wrong ...

 thx
 Koen

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/a50cc5ac-f548-4432-a673-9c02073d3542%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/a50cc5ac-f548-4432-a673-9c02073d3542%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gndED9G3tox3XGuJTwv97Jp9ioHK%3DL%3D6MhYydrpezWzxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available

['Roberto Lublinerman' via GWT Contributors]

There seems that some assertions in UnifyAST are not being satisfied in
incremental SDM but it runs fine (and correctly) if you turn off assertions.

On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote:

 I grabbed the RC and switched to use it from my IntelliJ project.

 When starting my run configuration using SDM, all seems well until the
 compiler dies (see below). What can I do to provide more information to
 help track this down? (Sorry, I cannot make the code available...)


 // Lots and lots of:
 //  Resolving ...
 //Found type ''
 //  Resolving method ...

  Finding entry point classes
  Assimilating generated source
 Generated source files...
com.google.gwt.lang.com_00046ao_00046foo_
 00046MyGwtModule_00045DEV__EntryMethodHolder
  Adding '1' new generated units
 Compiling...
Compilation completed in 0.00 seconds
 Added 1 units to cache since last cleanup.
 Removing invalidated units
 Wrote 1 units to persistent cache.
  [ERROR] Unexpected internal compiler error
 java.lang.AssertionError
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1407)
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414)
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1186)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1191)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1191)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1206)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1188)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at 

Re: [gwt-contrib] Re: GWT 2.7.0-RC1 is available

['Roberto Lublinerman' via GWT Contributors]

Yes. Will be fixed before final release.

On Thu, Oct 30, 2014 at 2:23 PM, jay j...@thegindins.com wrote:

 I'll give that a try...

 Will the issue be handled before the final release?

 jay

 On Thursday, October 30, 2014 11:47:54 AM UTC-7, Roberto Lublinerman wrote:

 There seems that some assertions in UnifyAST are not being satisfied in
 incremental SDM but it runs fine (and correctly) if you turn off assertions.

 On Wed, Oct 29, 2014 at 10:53 PM, jay j...@thegindins.com wrote:

 I grabbed the RC and switched to use it from my IntelliJ project.

 When starting my run configuration using SDM, all seems well until the
 compiler dies (see below). What can I do to provide more information to
 help track this down? (Sorry, I cannot make the code available...)


 // Lots and lots of:
 //  Resolving ...
 //Found type ''
 //  Resolving method ...

  Finding entry point classes
  Assimilating generated source
 Generated source files...
com.google.gwt.lang.com_00046ao_00046foo_
 00046MyGwtModule_00045DEV__EntryMethodHolder
  Adding '1' new generated units
 Compiling...
Compilation completed in 0.00 seconds
 Added 1 units to cache since last cleanup.
 Removing invalidated units
 Wrote 1 units to persistent cache.
  [ERROR] Unexpected internal compiler error
 java.lang.AssertionError
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1407)
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414)
  at com.google.gwt.dev.jjs.impl.UnifyAst.instantiate(UnifyAst.java:1414)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1186)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1191)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1226)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1191)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1733)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1747)
  at com.google.gwt.dev.jjs.impl.UnifyAst.flowInto(UnifyAst.java:1206)
  at com.google.gwt.dev.jjs.impl.UnifyAst.fullFlowIntoType(UnifyAst.java:
 1188)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1020)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010)
  at com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:
 1595)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  at com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  at com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  at com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.
 java:1010

Re: [gwt-contrib] Re: odd super dev mode times

['Roberto Lublinerman' via GWT Contributors]

John detected that behavior in the persistent unit cache and has a fix for
it.
On Oct 19, 2014 7:16 PM, Stephen Haberman stephen.haber...@gmail.com
wrote:


  ...and, right now, I can't even get the 3s time to kick in again.

 Ah ha...seems to be something with the PersistentUnitCache.

 When the recompile is 10-20s every time, I see output of:

 Wrote 4944 units to persistent cache
 Wrote 1 units to persistent cache
 (reload)
 Wrote 4944 units to persistent cache
 Wrote 1 units to persistent cache
 (reload)
 Wrote 4944 units to persistent cache
 Wrote 1 units to persistent cache

 I nuked my gwt-unitCache dir, and then see:

 (on startup)
 Wrote 4944 units to persistent cache
 (first load)
 Wrote 1 units to persisent cache
 ...this (Wrote 1 unit) repeated 100s of times...
 Purging cache files
 Wrote 6166 units to persistent cache
 Wrote 4945 units to persistent cache
 Wrote 1 units to persistent cache
 ...few more 1 units...
 (reload)
 Wrote 1 units to persistent cache
 (reload)
 Wrote 1 units to persistent cache

 I'm now getting the 3s reload. I restarted devmode 2-3x and it still
 worked great. However, on the 4th-5th restart, the old behavior came
 back. Nuking my gwt-unitCache re-fixed it.

 - Stephen


 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141019211649.6a1a0307%40sh9
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gk_0zZ2e5huLO9fKGE_uKBdoGDKQUqMjcm95fZgPjBChw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] odd super dev mode times

['Roberto Lublinerman' via GWT Contributors]

The time it takes to compile depends not only on how many files are
modified but also how big is the invalidation caused by the modification.
Depending what gets invalidated it might require running more generators or
(re) compiling many more types.

Also the first few compiles are also warming up the JVM, jit and all.

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnvMK1m8ET4TKtjWfdodrxEnE8P4cocehW2ozD2uhKpQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] class cast exception in ff 17

['Roberto Lublinerman' via GWT Contributors]

Can you isolate the bug and open an issue for it? If you upload a repro
case I'll take a look.

On Fri, Oct 3, 2014 at 11:52 AM, Stephen Haberman 
stephen.haber...@gmail.com wrote:

 Hey,

 I know FF17 is pretty old, but do we care about breakages in it? We
 noticed some client-side ClassCastExceptions in our logs that are
 from a user on FF17. The app works fine in FF latest.

 The exception is odd, because, according to the de-obfuscated stack
 trace, given a class hierarchy like:

class Base
class Foo extends Base
class Bar extends Base

 We are in new Foo(), from the Foo cstr we call the Base cstr, which
 calls Base.someMethod(). Base.someMethod() calls Base.anotherMethod().

 Now the bizarre thing is that we end up in *Bar*.anotherMethod(), and
 get a class cast exception.

 E.g. somehow we jumped subclasses, and went from executing code in
 Foo/Foo's base class to code that is in Bar.

 Which seems really odd. Which is why I mention it. If we don't care,
 that's fine, but it made me scratch my head for awhile.

 (Our production build is using a GWT snapshot from ~April, but I also
 reproduced it in our app with a GWT snapshot build from ~last week.)

 - Stephen

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/20141003135259.76c16354%40sh9
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkXtB3Ky3%3DFY11M0_E8MERpU0tKhkd2-C71wncG4RpTsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

['Roberto Lublinerman' via GWT Contributors]

Can you reproduce that from the command line in a regular compile? If so
can you post all the flags passed to the compiler?

On Wed, Oct 1, 2014 at 2:27 PM, Julien Dramaix julien.dram...@gmail.com
wrote:

 Am I the only one to have this problem ?

 On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix julien.dram...@gmail.com
  wrote:

 Dear GWT lovers,

 I've just tried to compile several projects with the last snapshot of GWT
 2.7.0 using the PRETTY mode flag and several permutations. I noticed that
 only one js file (corresponding to one permutation) is emitted with non
 obfuscated javascript. The other files for each other permutation contains
 obfuscated javascript.

 I've tested with GWT 2.6.1 and everything works as expected: all the
 files contain only non-obfuscated javascript.

 Julien


  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnRLixpdnwY8X-tsnRd4btdie20U_GCCx1i0p2s6KZ1CA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Compiler Faiure

['Roberto Lublinerman' via GWT Contributors]

This seems to be the error:

java.lang.IncompatibleClassChangeError: class
com.google.gwt.dev.javac.asm.CollectMethodData has interface
org.objectweb.asm.MethodVisitor as super class

and the problem seems to be that you have ASM  5 in your class path. (It
seems that MethodVisitor was an interface in ASM  4 and is now an abstract
class.

2.7 no longer rebases ASM

On Wed, Oct 1, 2014 at 2:33 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

 Hi all,

 Do anyone knows what could change lately which makes the compiler fail if
 jetty annotations is in your classpath.

 The way to reproduce is compiling any project which jetty-annotations.jar
 before  before gwt-dev.jar.

 Attached trace.



  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtxtLYTr43FBqwm7-CLFMkGVcS2Oi9-vPP6MdpkqqPw_w%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmTDSDYfCPzVg5o1AEXzHNcrXhLL91iWv_n%2BJsVJ-oNxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

['Roberto Lublinerman' via GWT Contributors]

I'll look into it.


Manolo,
Do you know what is the Building Unknown Task that is showing in our
jenkins instance?

On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
wrote:

 Roberto, in my case this is the command line:

 /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/bin/java
 -Xmx512m -classpath . . .  -Dgwt.persistentunitcachedir= target
 com.google.gwt.dev.Compiler -logLevel INFO -style PRETTY -war
 target/v-demo-1.0-SNAPSHOT -localWorkers 8 -draftCompile -XnocheckCasts
 -compileReport -XfragmentCount -1 -sourceLevel 1.7 -XjsInteropMode NONE
 -extra target/extra -gen v-demo/target/.generated
 com.vaadin.prototype.wc.gwt.Demo

 I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.





 On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino man...@apache.org
  wrote:

 I could verify the issue.
 A clue, It seems that the last emitted permutation is the only one
 un-obfuscated.

 As a workaround you can collapse-all-properties, and the result is PRETTY

 - Manolo

 On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix julien.dram...@gmail.com
  wrote:

 Am I the only one to have this problem ?

 On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

 Dear GWT lovers,

 I've just tried to compile several projects with the last snapshot of
 GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
 that only one js file (corresponding to one permutation) is emitted with
 non obfuscated javascript. The other files for each other permutation
 contains obfuscated javascript.

 I've tested with GWT 2.6.1 and everything works as expected: all the
 files contain only non-obfuscated javascript.

 Julien


  --
 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-contributors+unsubscr...@googlegroups.com
 .
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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



  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gkFyx%2B6FySa_i5on1GLTzf3tV9rLi7HOD3sHtdhgysyiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: [2.7.0-SNAPSHOT] Bug in compilation with pretty mode

['Roberto Lublinerman' via GWT Contributors]

Fixed. Review at https://gwt-review.googlesource.com/#/c/9432.

The issue is only present with -localWorkers  1 and all workers except the
first would get incorrect options.

On Wed, Oct 1, 2014 at 4:23 PM, Roberto Lublinerman rlu...@google.com
wrote:

 I'll look into it.


 Manolo,
 Do you know what is the Building Unknown Task that is showing in our
 jenkins instance?

 On Wed, Oct 1, 2014 at 2:49 PM, Manuel Carrasco Moñino man...@apache.org
 wrote:

 Roberto, in my case this is the command line:

 /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre/bin/java
 -Xmx512m -classpath . . .  -Dgwt.persistentunitcachedir= target
 com.google.gwt.dev.Compiler -logLevel INFO -style PRETTY -war
 target/v-demo-1.0-SNAPSHOT -localWorkers 8 -draftCompile -XnocheckCasts
 -compileReport -XfragmentCount -1 -sourceLevel 1.7 -XjsInteropMode NONE
 -extra target/extra -gen v-demo/target/.generated
 com.vaadin.prototype.wc.gwt.Demo

 I'm compiling with maven using gwt-maven-2.7-SNAPSHOT and trunk GWT.





 On Wed, Oct 1, 2014 at 11:44 PM, Manuel Carrasco Moñino 
 man...@apache.org wrote:

 I could verify the issue.
 A clue, It seems that the last emitted permutation is the only one
 un-obfuscated.

 As a workaround you can collapse-all-properties, and the result is PRETTY

 - Manolo

 On Wed, Oct 1, 2014 at 11:27 PM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

 Am I the only one to have this problem ?

 On Fri, Sep 26, 2014 at 11:46 PM, Julien Dramaix 
 julien.dram...@gmail.com wrote:

 Dear GWT lovers,

 I've just tried to compile several projects with the last snapshot of
 GWT 2.7.0 using the PRETTY mode flag and several permutations. I noticed
 that only one js file (corresponding to one permutation) is emitted with
 non obfuscated javascript. The other files for each other permutation
 contains obfuscated javascript.

 I've tested with GWT 2.6.1 and everything works as expected: all the
 files contain only non-obfuscated javascript.

 Julien


  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4hPmdnqisA62R387c%3D77bVNboxB%3DW9R3%3DBgTFYTtvhNw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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



  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAM28XAtsJqs-Cs%2Bvk0R70mabgyEr9pY%2BZzJM0TkJfMLKkOw6tw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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




-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmQcsR885h4CEtRvjCOfCnKi3jFvnJsDmzODo25J7Exqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: SDM -XcompilePerFile: initial feedback

[Roberto Lublinerman]

 So out of pure curiosity - are there obvious optimizations in the linker 
 which are still pending?


We have been thinking about strategies to incrementalize the work done by 
the linkers, one idea is to have a linker that outputs js for different 
Java classes to different resources and that could be incrementalized.


 For example, I noticed that a huge amount of time ( 50% of the whole 
 linking time) is spend in Saving source with extras, i.e. SourceSaver. 
 Given that these sources are only needed by the browser during a 
 sourcemap-based debugging session, can't they be served on the fly by the 
 code server rather than being pregenerated on disk during the 
 recompilation? There are debugging scenarios (in-IDE debugging with SDBG), 
 where these source files are not even needed and never requested from the 
 codeserver.

 I am currently working on this one. There are two options here: 1) serving 
source code directly without copying and 2) copying only changed sources. 
Option 1) would be the optimal in terms of compile time but it might result 
of a worse debugging experience (if you modify a source while debugging the 
source mapping will be out of date).
 

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/cc62d937-5db6-451a-b2d5-65982dcc9f5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Upgrading Checkstyle to 5.7 (Java 7 grammar support and more)

['Roberto Lublinerman' via GWT Contributors]

We upgraded to checkstyle 5.7 in trunk (
https://gwt-review.googlesource.com/#/c/6670/). If you checkout out trunk
or download the nighty builds (2.7.0-SNAPSHOP) from maven all the required
changes  (to ant, the style files, etc) are there.



On Sat, Jun 7, 2014 at 1:26 AM, Michael Prentice splak...@gmail.com wrote:

 Today, I was able to get Eclipse building the trunk with the latest
 Checkstyle v5.7 from http://eclipse-cs.sourceforge.net/update

 I was seeing a ton (1200-1900+) of OrderCheck and FieldCheck errors using
 Checkstyle 4.2 or 4.3 in Eclipse. But with 5.7, I am not seeing any errors.
 It does appear that Checkstyle 4.2 is still being used by Ant though.

 There was some discussion about upgrading Checkstyle last year here
 https://groups.google.com/forum/#!searchin/google-web-toolkit-contributors/checkstyle/google-web-toolkit-contributors/0aqmDB2tHfI/ZZTLRdinx-sJ
 .

 *Checkstyle 5.7 includes Java 7 grammar support, which is now supported
 (and the default) in gwt 2.6.0+.*


 *In order to upgrade the current .xml configuration files for Checkstyle,
 the following appear to be needed:*

 *PackageHtml* looks like it can just be changed to *JavadocPackage*.

 *GenericIllegalRegexp* looks like it can just be changed to
 *RegexpSingleline*. It needs to be pulled out of the TreeWalker module.

 *TabCharacter* needs to be replaced with *FileTabCharacter*. It needs to be 
 pulled out of the TreeWalker module and have the following added to it: 
 property name=fileExtensions value=java/

 *RegexpHeader* needs to be pulled out of the TreeWalker module and have the 
 following added to it: property name=fileExtensions value=java/

 There seems to be a bug with *SuppressionCommentFilter* and the use of 
 messageFormat AND checkFormat not properly working together. Removing 
 messageFormat seems to help for now. There is an issue about this here 
 https://github.com/checkstyle/checkstyle/issues/123.

 There are 4 files in gwt-user that break the *AvoidStarImport* check
 which will need to be fixed.


 From the checkstyle release notes:

 Removed the DoubleCheckedLocking check, as in Java 5 (and beyond), using the 
 volatile keyword addresses the issue. See here 
 http://jeremymanson.blogspot.com.au/2008/05/double-checked-locking.html for 
 more details.


 *Can this check be removed for gwt as well?*


 It looks like checkstyle-5.7-all.jar is already in gwt/tools/antlib/. So
 this would just mean a small change to trunk/common.ant.xml in addition to
 the configuration mentioned above.

 --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/dc4df58a-3381-4daf-961a-3e820fea50c5%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/dc4df58a-3381-4daf-961a-3e820fea50c5%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmgqOTr5FRhQ-qY66rF5RQ5W0KkdoJZA7w%2BV_shnFjieg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Add Object.clone as throwing implementation

['Roberto Lublinerman' via GWT Contributors]

The problem with implementing clone() at object is that it is an breaking
change because of the rules for JSOs. JSOs are required to implement (and
declare final) all Object methods because there is no dynamic dispatch. So
having clone() at Object implies either implementing it in JavaScriptObject
(and declare it final there), breaking all projects that have JSOs that
implement clone() or required all JSOs to implement clone() again breaking
all projects that have JSOs.


On Mon, May 26, 2014 at 8:10 AM, 'Daniel Kurka' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 I rolled the patch because it broke internal apps and it seemed to hard
 and not worthwhile to clean this up.
 I just imported the change and running some tests internally I get back
 once I can see what needs to be done.


 On Mon, May 26, 2014 at 11:37 AM, Rocco De Angelis rdeangeli...@gmail.com
  wrote:

 Hi all,

 I would like to added a clone method to the java.lang.Object class in the
 GWT SDK which simply throws a CloneNotSupportedException.
 This makes it possible to implement the clone method in subclasses.
 See: https://gwt-review.googlesource.com/#/c/6035/

 Daniel Kurka has already done a similar patch but without an adaption of
 GenerateJavaScriptAST.javahttps://gwt-review.googlesource.com/#/c/6035/1/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
  class.
 My patch is already in the review system but still not approved.
 Thomas Broyer started with the review and asked me why the patch of
 Daniel was reverted.
 I think that Daniel simply forgot the changes in the
 GenerateJavaScriptAST.javahttps://gwt-review.googlesource.com/#/c/6035/1/dev/core/src/com/google/gwt/dev/jjs/impl/GenerateJavaScriptAST.java
 .
 Some feedback would be nice :)

 BR
 Rocco




  --
 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-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/b2d067e8-f9c1-4fca-ab10-911e966b09f1%40googlegroups.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/b2d067e8-f9c1-4fca-ab10-911e966b09f1%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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

 --
 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-contributors+unsubscr...@googlegroups.com.
  To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiovq8QnUqyF0a9wZU7ydzqFwpp0Yg72SibBaW7GKt%2BR%3Dg%40mail.gmail.comhttps://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiovq8QnUqyF0a9wZU7ydzqFwpp0Yg72SibBaW7GKt%2BR%3Dg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .

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


-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gmdfh9AWd5%3D3bRNRzF_Os0bhKg1C4KPE0%2BiZtdnvNRQzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Nightly snapshot being uploaded to sonatype maven repository

['Roberto Lublinerman' via GWT Contributors]

Those maven snapshots were done while testing. The logs for the failed
builds are not showing maven uploads.


On Wed, Apr 30, 2014 at 3:45 AM, Jens jens.nehlme...@gmail.com wrote:

 Thats cool, however it seems like that builds with failing tests are
 pushed out to Maven? Jenkins build #27 and #28 from today (30.04) have
 failing tests but still there is a maven snapshot for today (30.04) which
 seems to be Jenkins build #28.

 http://107.178.215.71:8080/job/gwt/

 https://oss.sonatype.org/content/groups/google/com/google/gwt/gwt/2.7.0-SNAPSHOT/


 -- J.

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.

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


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] collapse-all-properties and symbolMaps

[Roberto Lublinerman]

AFAIK I see no reason why symbolMaps are incompatible with
collapse-all-properties.

SymbolMaps seem to be controlled by compiler.useSymbolMap property and are
emitted by SymbolMapsLinker.

Perhaps on one of the permutations that property is set to false? Line 261
in SymbolMapsLinker.java seems to only care about the last value of the
property.

I am not familiar with this part of GWT but looking at
SymbolMapsLinker.link there seems to be a pathway where if onePermutation
is false nothing is emitted.




On Tue, Apr 8, 2014 at 11:59 PM, Manuel Carrasco Moñino
man...@apache.orgwrote:

 Hi all,

 Does someone know what is the reason for disabling symbolMaps when
 collapse-all-properties is set?

 Is that a desired constrain, or just a bug?

 I'm not familiar with this part of the code and I would like to take a
 look so as it can be fixed, could someone point where to have a look?

 - Manolo

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Obfuscated compilation

[Roberto Lublinerman]

It is now a know problem. In fact from 2.5 to 2.6 there have been small
improvements in compilation speed (on large projects).

W.r.t. the exception in obfuscated mode, did you observe the problem on one
permutation or in multiple?



On Wed, Apr 2, 2014 at 9:52 PM, Michael Vogt i...@michaelvogt.eu wrote:

 Hello.

 I was finally able to switch to GWT 2.6 for the project I am working
 on. Immediate observation was, that compilation takes now more than
 twice as long as before.

 Also, when compiling with style obfuscated, the application throws an
 exception directly at application start. Runs without problems with
 style Detailed and Pretty. Is this a known problem and fixed with
 2.6.1?


 Greetings,
 Michael

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Obfuscated compilation

[Roberto Lublinerman]

Sorry for the mistype. I meant it is NOT a known problem. If you can
provide an example that reproduces that behaviour I would love to debug it.


On Thu, Apr 3, 2014 at 9:35 AM, Roberto Lublinerman rlu...@google.comwrote:

 It is now a know problem. In fact from 2.5 to 2.6 there have been small
 improvements in compilation speed (on large projects).

 W.r.t. the exception in obfuscated mode, did you observe the problem on
 one permutation or in multiple?



 On Wed, Apr 2, 2014 at 9:52 PM, Michael Vogt i...@michaelvogt.eu wrote:

 Hello.

 I was finally able to switch to GWT 2.6 for the project I am working
 on. Immediate observation was, that compilation takes now more than
 twice as long as before.

 Also, when compiling with style obfuscated, the application throws an
 exception directly at application start. Runs without problems with
 style Detailed and Pretty. Is this a known problem and fixed with
 2.6.1?


 Greetings,
 Michael

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Obfuscated compilation

[Roberto Lublinerman]

A type error like might just be equivalent to a java NullPointerException.
Once the application is compiled to JavaScript instead of producing NPEs it
produces TypeErrors. If you run it with -style PRETTY it might give you a
hint where in the code the type error is ocurring and you might be able to
debug it in the browser...


On Thu, Apr 3, 2014 at 9:45 PM, Michael Vogt i...@michaelvogt.eu wrote:

 Roberto, thanks for your answer.

 Regarding the compile time, it looks like my computer had a bad day
 yesterday. Compile speed is now around 10% faster than with 2.5.
 Sorry.

 As the exception I see is not know, here some more information about
 my environment here. I was trying to find the code that fails by
 reducing the executed code, but was not successful. As it seems to me
 right now, it feels like a problem with GIN (2.1.2). Here is some
 information about what I see:

 - The problem exists with all the browsers I have here the same way -
 FireFox 26, Chrome 33 and IE 11
 - This line brakes with Uncaught TypeError: Cannot read property 'b'
 of undefined 
 A2(38,10,bwb);function Bf(a,b){Xeb(a.b,b,false)}
 - In another occasion, the message is Uncaught TypeError: Cannot call
 method 'Je' of null 
 function qz(a){var
 b;b=qy;if(b){if(b==dz){return}a.be()+spb;xy(a);a.be
 ();null.Je();return}pz(nN(a,48)?lN(a,48).ce():a)}


 I'm on Windows 7, working with IntelliJ IDEA 13.1, using Java 7. I
 also made sure that I don't have a jar of GWT 2.5 as a leftover
 somewhere in the project, so I hope this is not a stupid configuration
 error. The application runs fine.

 Please let me know what I need to provide to help you reproduce the
 problem.


 Greetings,
 Michael

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Obfuscated compilation

[Roberto Lublinerman]

It would be interesting to look at the Symbol map corresponding to the
breaking permutation and see what are the functions Bf and Xeb.


On Thu, Apr 3, 2014 at 10:11 PM, Michael Vogt i...@michaelvogt.eu wrote:

 Just verified: When compiling the same code with style detailed, there
 is no exception thrown anywhere .
 Also, running the application with super dev mode works without problems.

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Change in gwt[master]: Slightly optimize System.nativeArraycopy for the common case.

[Roberto Lublinerman]

I don't know whether it is only me or a general problem but in my local
repo Gerrit seems to be acting up, pushes take forever and end up in error.


On Tue, Feb 18, 2014 at 8:24 PM, Roberto Lublinerman rlu...@google.comwrote:

 Roberto Lublinerman has uploaded a new patch set (#2).

 Change subject: Slightly optimize System.nativeArraycopy for the common
 case.
 ..

 Slightly optimize System.nativeArraycopy for the common case.

 Only make a temporary copy of the input when it's the same as the output.
 Performance: http://jsperf.com/java-system-arraycopy/2

 Bug: issue 8239
 Change-Id: I86a6c512e4670594c1e6e4cb9418cbac029152f1
 ---
 M user/super/com/google/gwt/emul/java/lang/System.java
 1 file changed, 8 insertions(+), 4 deletions(-)


 --
 To view, visit https://gwt-review.googlesource.com/6439
 To unsubscribe, visit https://gwt-review.googlesource.com/settings

 Gerrit-MessageType: newpatchset
 Gerrit-Change-Id: I86a6c512e4670594c1e6e4cb9418cbac029152f1
 Gerrit-PatchSet: 2
 Gerrit-Project: gwt
 Gerrit-Branch: master
 Gerrit-Owner: Roberto Lublinerman rlu...@google.com
 Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] One time whitespace cleanup.

[Roberto Lublinerman]

api-checker is in!


On Wed, Feb 12, 2014 at 6:07 PM, Goktug Gokdogan gok...@google.com wrote:

 I have plenty of patches that were waiting for apichecker. Can you hold of
 until next week?


 On Wed, Feb 12, 2014 at 12:35 PM, John Stalcup stal...@google.com wrote:

 I'm going to do a one time automated whitespace cleanup of the GWT
 codebase.

 If you have a large (1000+ line) code review in progress, let me know and
 I'll hold off for a day or two to avoid conflicts.

 You can ignore whitespace changes in blame with git blame -w.

 John

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Cannot build any project since 5a972863

[Roberto Lublinerman]

Hi Jay,

It would be interesting to see why JsSymbolResolver did not resolve the
ident into a JsName. I would check if that JsNameRef object created AFTER
JsSymbolResolver is called.

Good luck,
Roberto.


On Fri, Jan 24, 2014 at 8:14 AM, jay j...@thegindins.com wrote:

 I'll try over the weekend to come up with a repro project. While I'm
 working on that, is there anything I can look for in the compiler? I'm able
 to build and use my locally built GWT compiler, so it's easy to stick in
 some debug statements and inspect what's going on.

 thanks,

 jay


 On Thursday, January 23, 2014 9:30:40 AM UTC-8, Roberto Lublinerman wrote:

 The bug in the post is not due to the issue being discussed in the
 thread. If you can attach a small project that repros the bug you are
 getting, I'll take a look.

 Best,
 Roberto.


 On Wed, Jan 22, 2014 at 10:30 PM, jay jay.g...@gmail.com wrote:

 I realize that about the only thing in common is that the GWT compiler
 is throwing an NPE, but I have to ask... Is there any chance that this
 issue has the same root cause as the NPE I reported in this 
 posthttps://groups.google.com/forum/#!topic/google-web-toolkit-contributors/1vA7gYrCjvo
  and
 this bughttps://code.google.com/p/google-web-toolkit/issues/detail?id=8536
 ?

 thanks,

 jay


 On Wednesday, January 22, 2014 11:43:22 AM UTC-8, Andrés Testi wrote:

 Thanks!

 - Andrés Testi

 El miércoles, 22 de enero de 2014 16:39:45 UTC-3, John Stalcup escribió:

 Yeah. It seems that CompilePermsServer doesn't have a ModuleDef
 instance, so it's not populating compilerContext.getModule(), which laters
 causes compilerContext.getModule().isMonolithic() to fail.

 I'm working on a fix.


 On Wed, Jan 22, 2014 at 11:26 AM, Andrés Testi 
 andres@gmail.comwrote:

 Hi John:

 I'm running ant without explicit target (build by default). No
 explicit flags. I got the same exception in two isolated environments
 (ubuntu 13.10 with OpenJDK, and Windows 8 with Oracle JDK). The exception
 is throwed when the script tries to compile the DynaTable sample.
  CompilerContext.getModule() seems to return null here:
 https://github.com/gwtproject/gwt/blob/master/dev/
 core/src/com/google/gwt/dev/jjs/UnifiedAst.java#L137

 - Andrés Testi

 El miércoles, 22 de enero de 2014 15:45:35 UTC-3, John Stalcup
 escribió:

 Yeah that does look to be related to my commit.

 Which compiler entry point are you launching and with what flags? I
 updated Compiler.java, CompilePerms.java, etc etc to property setup the
 module property of the compilerContext object, but it looks like I 
 missed
 somewhere.

 John


 On Wed, Jan 22, 2014 at 4:07 AM, Honza Rameš ram...@gmail.comwrote:

 Hello everyone,
 I'm using master for my projects and after I updated to commit
 5a972863 (Added monolithic/separate branching to 
 JavaToJavaScriptCompiler)
 suddenly I wasn't able to compile any of my GWT projects (in Eclipse, 
 see
 error message bellow). I'm using jdk_1.7 and older commit (8ef35362) 
 works
 just fine. Did any of you encountered build breakage recently, is there
 some workaround you know of?

 DevMode works OK with this commit. I have Eclipse 3.7 and GPE
 3.5.1. While compiling simple project I noticed that some of the
 permutations compile just fine. Could this be caused by IE6 
 permutation, I
 do have some deferred binding rules in my module targeting the IE6.

 Error messge:
  [ERROR] Compile failed
  java.lang.NullPointerException
  at com.google.gwt.dev.jjs.Unified
 Ast.compilePermutation(UnifiedAst.java:137)
  at com.google.gwt.dev.CompilePerms.compile(
 CompilePerms.java:196)
  at com.google.gwt.dev.CompilePermsServer.
 compilePermutation(CompilePermsServer.java:307)
  at com.google.gwt.dev.CompilePermsServer.run(
 CompilePermsServer.java:274)
  at com.google.gwt.dev.CompilePermsServer.main(
 CompilePermsServer.java:237)
   [ERROR] Error from external worker
 java.lang.NullPointerException
 at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(Unified
 Ast.java:137)
 at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:19
 6)
 at com.google.gwt.dev.CompilePermsServer.compilePermutation(Com
 pilePermsServer.java:307)
 at com.google.gwt.dev.CompilePermsServer.run(CompilePermsServer
 .java:274)
 at com.google.gwt.dev.CompilePermsServer.main(CompilePermsServe
 r.java:237)
   [ERROR] Unrecoverable exception, shutting down
 com.google.gwt.core.ext.UnableToCompleteException: (see previous
 log entries)
 at com.google.gwt.dev.ExternalPermutationWorkerFactory$External
 PermutationWorker.compile(ExternalPermutationWorkerFactory.
 java:156)
 at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerTh
 read.run(PermutationWorkerFactory.java:73)
 at java.lang.Thread.run(Thread.java:744)

 Any help would be appreciated.

 Regards

 Honza Rames

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 You received

Re: [gwt-contrib] Cannot build any project since 5a972863

[Roberto Lublinerman]

The bug in the post is not due to the issue being discussed in the thread.
If you can attach a small project that repros the bug you are getting, I'll
take a look.

Best,
Roberto.


On Wed, Jan 22, 2014 at 10:30 PM, jay jay.gin...@gmail.com wrote:

 I realize that about the only thing in common is that the GWT compiler is
 throwing an NPE, but I have to ask... Is there any chance that this issue
 has the same root cause as the NPE I reported in this 
 posthttps://groups.google.com/forum/#!topic/google-web-toolkit-contributors/1vA7gYrCjvo
  and
 this bughttps://code.google.com/p/google-web-toolkit/issues/detail?id=8536
 ?

 thanks,

 jay


 On Wednesday, January 22, 2014 11:43:22 AM UTC-8, Andrés Testi wrote:

 Thanks!

 - Andrés Testi

 El miércoles, 22 de enero de 2014 16:39:45 UTC-3, John Stalcup escribió:

 Yeah. It seems that CompilePermsServer doesn't have a ModuleDef
 instance, so it's not populating compilerContext.getModule(), which laters
 causes compilerContext.getModule().isMonolithic() to fail.

 I'm working on a fix.


 On Wed, Jan 22, 2014 at 11:26 AM, Andrés Testi andres@gmail.comwrote:

 Hi John:

 I'm running ant without explicit target (build by default). No
 explicit flags. I got the same exception in two isolated environments
 (ubuntu 13.10 with OpenJDK, and Windows 8 with Oracle JDK). The exception
 is throwed when the script tries to compile the DynaTable sample.
  CompilerContext.getModule() seems to return null here:
 https://github.com/gwtproject/gwt/blob/master/
 dev/core/src/com/google/gwt/dev/jjs/UnifiedAst.java#L137

 - Andrés Testi

 El miércoles, 22 de enero de 2014 15:45:35 UTC-3, John Stalcup escribió:

 Yeah that does look to be related to my commit.

 Which compiler entry point are you launching and with what flags? I
 updated Compiler.java, CompilePerms.java, etc etc to property setup the
 module property of the compilerContext object, but it looks like I missed
 somewhere.

 John


 On Wed, Jan 22, 2014 at 4:07 AM, Honza Rameš ram...@gmail.com wrote:

 Hello everyone,
 I'm using master for my projects and after I updated to commit
 5a972863 (Added monolithic/separate branching to 
 JavaToJavaScriptCompiler)
 suddenly I wasn't able to compile any of my GWT projects (in Eclipse, see
 error message bellow). I'm using jdk_1.7 and older commit (8ef35362) 
 works
 just fine. Did any of you encountered build breakage recently, is there
 some workaround you know of?

 DevMode works OK with this commit. I have Eclipse 3.7 and GPE 3.5.1.
 While compiling simple project I noticed that some of the permutations
 compile just fine. Could this be caused by IE6 permutation, I do have 
 some
 deferred binding rules in my module targeting the IE6.

 Error messge:
  [ERROR] Compile failed
  java.lang.NullPointerException
  at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(
 UnifiedAst.java:137)
  at com.google.gwt.dev.CompilePerms.compile(
 CompilePerms.java:196)
  at com.google.gwt.dev.CompilePermsServer.
 compilePermutation(CompilePermsServer.java:307)
  at com.google.gwt.dev.CompilePermsServer.run(
 CompilePermsServer.java:274)
  at com.google.gwt.dev.CompilePermsServer.main(
 CompilePermsServer.java:237)
   [ERROR] Error from external worker
 java.lang.NullPointerException
 at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(Unified
 Ast.java:137)
 at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:196)
 at com.google.gwt.dev.CompilePermsServer.compilePermutation(Com
 pilePermsServer.java:307)
 at com.google.gwt.dev.CompilePermsServer.run(CompilePermsServer
 .java:274)
 at com.google.gwt.dev.CompilePermsServer.main(CompilePermsServe
 r.java:237)
   [ERROR] Unrecoverable exception, shutting down
 com.google.gwt.core.ext.UnableToCompleteException: (see previous log
 entries)
 at com.google.gwt.dev.ExternalPermutationWorkerFactory$
 ExternalPermutationWorker.compile(ExternalPermutationWorkerFacto
 ry.java:156)
 at com.google.gwt.dev.PermutationWorkerFactory$Manager$
 WorkerThread.run(PermutationWorkerFactory.java:73)
 at java.lang.Thread.run(Thread.java:744)

 Any help would be appreciated.

 Regards

 Honza Rames

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscribe@
 googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscribe@
 googlegroups.com.
 For more options, visit 

Re: Re: [gwt-contrib] Can't build trunk with Java 6?

[Roberto Lublinerman]

Some changes to sourcemap generation require a version newer than 20131014.
The sourcemap part of the closure tools can probably be compiled with as
Java 6.




On Fri, Jan 17, 2014 at 9:12 AM, Thomas Broyer t.bro...@gmail.com wrote:



 On Friday, January 17, 2014 3:59:58 PM UTC+1, Artur Signell wrote:

 Any ideas how this could/will be resolved? Closure compiler dropped
 support for Java 6 in the 20131118 release (https://code.google.com/p/
 closure-compiler/wiki/Releases). But reverting to 20131014 seems to
 require some work.


 Maybe we could re-build them with source=1.6 target=1.6? Possibly they
 didn't introduce too much Java7-isms to the codebase in the 20131118
 release as the move to Java 7 was introduced only 4 days before:
 https://code.google.com/p/closure-compiler/source/detail?r=948fdc03049a358e67565aa72f09aa041cb9b15a


 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[gwt-contrib] Re: Can't build trunk with Java 6?

[Roberto Lublinerman]

Yep, I have just checked and sourcemap-rebased.jar is version 51.0 (i.e.
compiled with Java7). GWT takes this dependency from the public closure
release.


On Thu, Jan 9, 2014 at 3:13 PM, Jens jens.nehlme...@gmail.com wrote:

  Looks like IE6 hasn't been completely removed?


 Oh that reminds me of my comment I have done in
 https://gwt-review.googlesource.com/#/c/5055/ after it was already
 merged. The warning is caused by the IE 9 permutation but as the compiled
 code works I had forget about it.


 -- J.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Roberto Lublinerman]

It seems that the build script needs to pass -sourceLevel 6 when compiling
.gwtars (which we seem to ship incompiled form). I think I saw a patch or
email regarding that issue.


On Mon, Dec 9, 2013 at 8:17 AM, Matthew Dempsky mdemp...@google.com wrote:

 Hm, so is building with Java 6 a new requirement due to how we implemented
 Java 7 support in GWT?  I thought I used Java 7 to build the GWT 2.5.1
 release too, but I can make sure to use Java 6 instead going forward to
 build releases/release candidates/snapshots.


 On Mon, Dec 9, 2013 at 7:40 AM, Colin Alworth niloc...@gmail.com wrote:

 This system property isn't listed when either dev mode or the compiler
 runs because it is a system property, not a program arg. It should be
 provided with the other VM args when you start Java. These aren't listed as
 part of the normal properties, but are documented here:
 http://code.google.com/p/google-web-toolkit/wiki/JavaSystemPropertiesAndGwt

 We probably should migrate that table (and expand it?), but for the most
 part these are used to tweak internals that shouldn't normally be needed.
 In the case of the issue I'm pointing out with java6, it appears that this
 issue is only due to a build problem when the RC was originally compiled.
 The only other flag I use in the list with any regularity is
 gwt.jjs.traceMethods, which lets you see what the compiler is doing with
 each method as it works.


 On Sun, Dec 8, 2013 at 5:28 PM, Juan Pablo Gardella 
 gardellajuanpa...@gmail.com wrote:

 Thanks Thomas!


 2013/12/8 Thomas Broyer t.bro...@gmail.com



 On Sunday, December 8, 2013 2:12:31 PM UTC+1, Thomas Broyer wrote:


 On Saturday, December 7, 2013 7:42:42 PM UTC+1, juan_pablo_gardella
 wrote:

 HostedMode appears in http://www.gwtproject.org/doc/latest/
 DevGuideCompilingAndDebugging.html at the section Development Mode
 Options.


 Will fix.


 See https://gwt-review.googlesource.com/5651

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com
 .
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 218.248.6165
 niloc...@gmail.com

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Roberto Lublinerman]

Hi Colin,

Did you do ant clean? I find it strange that the resource points to
Matthew's hard drive, as if Impl was precompiled by him (and in that case
probably is consistent that the version is 51.0).

I build from scratch in my laptop (only has java 1.6) and builds and tests
run fine. Is there a specific application that you are trying to build?




On Thu, Dec 5, 2013 at 9:23 PM, Colin Alworth niloc...@gmail.com wrote:

 I'm still running into trouble with the major version of the compiled
 classes being 51, so I'm unable to gwt 2.6.0-rc3 to work under jdk 1.6. As
 before, I was able to confirm that the actual .class files are compiled
 correctly, but yet I get fatal errors in attempting to run dev mode.
 Testing so far is on a mac with 1.6.0_65:

 $ java -version
 java version *1.6.0_65*
 Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
 Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

 $ javap -v com.google.gwt.core.client.impl.Impl | head
 Compiled from Impl.java
 public final class com.google.gwt.core.client.impl.Impl extends
 java.lang.Object
   SourceFile: Impl.java
   InnerClass:
public abstract #77= #76 of #170; //UncaughtExceptionHandler=class
 com/google/gwt/core/client/GWT$UncaughtExceptionHandler of class
 com/google/gwt/core/client/GWT
   minor version: 0
   major version: *50*
   Constant pool:
 const #1 = Method#61.#163;//  java/lang/Object.init:()V
 const #2 = Field#55.#164;//
 com/google/gwt/core/client/impl/Impl.unloadSupport:Lcom/google/gwt/core/client/impl/UnloadSupport;

 When in dev mode, I've seen this error:
 22:44:37.233 [ERROR] [com.example.SampleProject] Unable to load module
 entry point class null (see associated exception for details)
 java.lang.UnsupportedClassVersionError:
 com/google/gwt/core/client/impl/Impl : Unsupported major.minor version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at
 com.google.gwt.dev.shell.ModuleSpace.loadClassFromSourceName(ModuleSpace.java:670)
 at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:359)
 at
 com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:200)
 at
 com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526)
 at
 com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
 at java.lang.Thread.run(Thread.java:695)

 When running unit tests in dev mode with HtmlUnit, I've seen this:
 [ERROR] Unable to load module entry point class null (see associated
 exception for details)
 [junit] java.lang.UnsupportedClassVersionError:
 com/google/gwt/core/client/impl/Impl : Unsupported major.minor version 51.0
 [junit] Dec 5, 2013 10:51:41 PM
 com.gargoylesoftware.htmlunit.WebConsole info
 [junit] at java.lang.ClassLoader.defineClass1(Native Method)
 [junit] INFO: /launch error: Failed to load module
 com.example.SampleProject.JUnit.
 [junit] at
 java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 [junit] Please see the log for details.
 [junit] at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 [junit] at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 [junit] at
 com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121)
 [junit] at
 com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194)
 [junit] at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 [junit] at java.lang.Class.forName0(Native Method)
 [junit] at java.lang.Class.forName(Class.java:249)
 [junit] at
 com.google.gwt.dev.shell.ModuleSpace.loadClassFromSourceName(ModuleSpace.java:670)
 [junit] at
 com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:359)
 [junit] at
 com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:200)
 [junit] at
 com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526)
 [junit] at
 com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
 [junit] at java.lang.Thread.run(Thread.java:695)

 It has been driving me nuts trying to track down what mistake I could
 possibly be making - I've tried explicitly adding -sourceLevel 1.6 to the
 arguments (which parses correctly, I set breakpoints to avoid the 

Re: [gwt-contrib] Re: 2.6.0-rc3

[Roberto Lublinerman]

It seems that we need to build the release with -sourceLevel 6 for it to
work with Java 6.


On Thu, Dec 5, 2013 at 10:43 PM, Colin Alworth niloc...@gmail.com wrote:

 Sorry for being unclear - I'm building/testing an application that makes
 use of GWT while still on Java6, not building/testing GWT itself. I'm
 trying to sanity test rc3 as a candidate for a final release of 2.6.0, and
 as far as my testing goes, this is the only point it is failing.

 To clarify the point about the references to Matthew's machine, unzip the
 gwt 2.6.0-rc3 download on code.google.com, unpack the gwt-user.jar file,
 and try this:

 $ strings com/google/gwt/core/Core.gwtar  | grep file | head
 fileNameq

 bfile:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/google/gwt/core/client/AsyncProvider.javat
 fileNameq

 ]file:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/google/gwt/core/client/Callback.javat
 fileNameq

 jfile:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/google/gwt/core/client/CodeDownloadException.javat
 fileNameq

 ]file:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/google/gwt/core/client/Duration.javat
 fileNameq
 fileNameq


 On Friday, December 6, 2013 12:10:10 AM UTC-6, Roberto Lublinerman wrote:

 Hi Colin,

 Did you do ant clean? I find it strange that the resource points to
 Matthew's hard drive, as if Impl was precompiled by him (and in that case
 probably is consistent that the version is 51.0).

 I build from scratch in my laptop (only has java 1.6) and builds and
 tests run fine. Is there a specific application that you are trying to
 build?




 On Thu, Dec 5, 2013 at 9:23 PM, Colin Alworth nilo...@gmail.com wrote:

 I'm still running into trouble with the major version of the compiled
 classes being 51, so I'm unable to gwt 2.6.0-rc3 to work under jdk 1.6. As
 before, I was able to confirm that the actual .class files are compiled
 correctly, but yet I get fatal errors in attempting to run dev mode.
 Testing so far is on a mac with 1.6.0_65:

 $ java -version
 java version *1.6.0_65*
 Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
 Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

 $ javap -v com.google.gwt.core.client.impl.Impl | head
 Compiled from Impl.java
 public final class com.google.gwt.core.client.impl.Impl extends
 java.lang.Object
   SourceFile: Impl.java
   InnerClass:
public abstract #77= #76 of #170; //UncaughtExceptionHandler=class
 com/google/gwt/core/client/GWT$UncaughtExceptionHandler of class
 com/google/gwt/core/client/GWT
   minor version: 0
   major version: *50*
   Constant pool:
 const #1 = Method#61.#163;//  java/lang/Object.init:()V
 const #2 = Field#55.#164;//  com/google/gwt/core/client/
 impl/Impl.unloadSupport:Lcom/google/gwt/core/client/impl/UnloadSupport;

 When in dev mode, I've seen this error:
 22:44:37.233 [ERROR] [com.example.SampleProject] Unable to load module
 entry point class null (see associated exception for details)
 java.lang.UnsupportedClassVersionError: com/google/gwt/core/client/impl/Impl
 : Unsupported major.minor version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 at com.google.gwt.dev.shell.CompilingClassLoader.findClass(
 CompilingClassLoader.java:1121)
 at com.google.gwt.dev.shell.CompilingClassLoader.loadClass(
 CompilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at com.google.gwt.dev.shell.ModuleSpace.loadClassFromSourceName(
 ModuleSpace.java:670)
 at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:359)
 at com.google.gwt.dev.shell.OophmSessionHandler.loadModule(
 OophmSessionHandler.java:200)
 at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(
 BrowserChannelServer.java:526)
 at com.google.gwt.dev.shell.BrowserChannelServer.run(
 BrowserChannelServer.java:364)
 at java.lang.Thread.run(Thread.java:695)

 When running unit tests in dev mode with HtmlUnit, I've seen this:
 [ERROR] Unable to load module entry point class null (see associated
 exception for details)
 [junit] java.lang.UnsupportedClassVersionError:
 com/google/gwt/core/client/impl/Impl : Unsupported major.minor version
 51.0
 [junit] Dec 5, 2013 10:51:41 PM com.gargoylesoftware.htmlunit.WebConsole
 info
 [junit] at java.lang.ClassLoader.defineClass1(Native Method)
 [junit] INFO: /launch error: Failed to load module
 com.example.SampleProject.JUnit.
 [junit] at java.lang.ClassLoader.defineClassCond(ClassLoader.
 java:637)
 [junit] Please see the log for details.
 [junit] at java.lang.ClassLoader.defineClass(ClassLoader.java:
 621)
 [junit

Re: [gwt-contrib] Re: Problem on sample Validation due to missing class in gwt-servlet

[Roberto Lublinerman]

On Wed, Nov 13, 2013 at 9:33 AM, Thomas Broyer t.bro...@gmail.com wrote:



 On Wednesday, November 13, 2013 5:41:12 PM UTC+1, Cristiano wrote:

 Hi All,

 I then think that it is needed a patch to include guava-15.0-rebased.jar,
 sourcemap-rebased.jar, protobuf-java-rebased-2.5.0.jar and
 streamhtmlparser-jsilver-r10-1.5-rebased.jar in gwt-servlet.jar


 No, not protobuf, it's only used for DevMode's remote UI (what makes the
 Dev Mode view in Eclipse possible)

 Guava is only needed for SafeHtml and SafeUri, so it'd be better to
 provide guava-less implementation of the two classes that use it; except if
 it's also needed for sourcemap, in which case it's OK to put it into
 gwt-servlet.


Guava is used by sourcemap so it must be provided as well.

@Cristiano would you want to make the patch yourserf? If so just add me as
a reviewer

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] GWT 2.6 and Java 6

[Roberto Lublinerman]

You are right, there should be an extra option -sourceLevel auto and that
should be the default for devmode.

On Nov 8, 2013, at 17:47, Colin Alworth niloc...@gmail.com wrote:

Thanks Roberto, I'll give that a shot. I normally work with Java 7, but we
want our code to work with anyone who chooses to use Java 6 as well - and I
surmised that GWT had the same goal.

Would it make sense to consider a warning indicating that the flag is
needed with Java 6, or auto-detecting that Java 6 is running so a
JavaScriptObject$ compiled for 7 can't possibly work?

On Friday, November 8, 2013 6:01:40 PM UTC-6, Roberto Lublinerman wrote:

 You should be able to invoke devmode with -sourceLevel 6.

 Roberto Lublinerman | Software Engineer | rlu...@google.com javascript:
  | 408-500-9148


 On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth nilo...@gmail.comjavascript:
  wrote:

 I'm not yet convinced that this isn't either a) a workspace issue or b) a
 decision the community reached and I missed, but I figured I should stick
 it out there and see if someone can correct me.

 I've just brought our project up to date with GWT 2.6.0-rc1 from maven,
 and I can verify that the class files have magic number 50.0 set on them,
 indicating Java 6. I can compile the project with a Java 6 jdk, and gwtc
 behaves as expected, but I can't run dev mode. The error I get usually goes
 a little like this:

 ERROR: Unable to initialize static dispatcher
 java.lang.UnsupportedClassVersionError:
 com/google/gwt/core/client/JavaScriptObject$ : Unsupported major.minor
 version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at com.google.gwt.dev.shell.JsValueGlue.set(JsValueGlue.java:220)

 The magic number 51.0 indicates Java7 - how is it that while I'm running
 Java 6, I am generating Java 7-only classes?

 My working theory is that since we moved some internals to be Java 7
 capable (somewhere around https://gwt.googlesource.com/gwt/+/e4f6142 or
 a related commit), it was set as the default. My question: do we intend to
 require Java 7 for dev mode (and therefore also GWTTestCase run in dev
 mode), but allow Java 6 for essentially everything else?

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.comjavascript:
 .
 For more options, visit https://groups.google.com/groups/opt_out.


  --
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] GWT 2.6 and Java 6

[Roberto Lublinerman]

You should be able to invoke devmode with -sourceLevel 6.

Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148


On Fri, Nov 8, 2013 at 3:31 PM, Colin Alworth niloc...@gmail.com wrote:

 I'm not yet convinced that this isn't either a) a workspace issue or b) a
 decision the community reached and I missed, but I figured I should stick
 it out there and see if someone can correct me.

 I've just brought our project up to date with GWT 2.6.0-rc1 from maven,
 and I can verify that the class files have magic number 50.0 set on them,
 indicating Java 6. I can compile the project with a Java 6 jdk, and gwtc
 behaves as expected, but I can't run dev mode. The error I get usually goes
 a little like this:

 ERROR: Unable to initialize static dispatcher
 java.lang.UnsupportedClassVersionError:
 com/google/gwt/core/client/JavaScriptObject$ : Unsupported major.minor
 version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121)
 at
 com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at com.google.gwt.dev.shell.JsValueGlue.set(JsValueGlue.java:220)

 The magic number 51.0 indicates Java7 - how is it that while I'm running
 Java 6, I am generating Java 7-only classes?

 My working theory is that since we moved some internals to be Java 7
 capable (somewhere around https://gwt.googlesource.com/gwt/+/e4f6142 or a
 related commit), it was set as the default. My question: do we intend to
 require Java 7 for dev mode (and therefore also GWTTestCase run in dev
 mode), but allow Java 6 for essentially everything else?

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Gerrit presubmit changes

[Roberto Lublinerman]

Fantastic.



On Sun, Oct 20, 2013 at 9:28 PM, Stephen Haberman
step...@exigencecorp.comwrote:


 Wow, that sounds awesome, Matthew. Great work. I'm looking forward to
 hopefully *not* triggering this great feedback. :-)

 - Stephen

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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-contributors+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: packages com.google.gwt.thirdparty.*

[Roberto Lublinerman]

On Sun, Oct 20, 2013 at 3:21 PM, Thomas Broyer t.bro...@gmail.com wrote:

See $GWT_TOOLS/lib/eclipse/README.jdt-upgrade (last paragraph), and
 comments in https://gwt-review.googlesource.com/#/c/2361/1/dev/build.xml (if
 you understand them; reading them now, I don't ;-) )


In retrospective I am not sure if extracting jdtCompilerAdapter.jar from
JDT is really needed.

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[gwt-contrib] Re: Can someone explain me why I get the following error?

[Roberto Lublinerman]

Seems to point that JavaScriptObject.class was compiled in java 7 mode but 
the codeserver is running in a java 6 vm.

On Wednesday, October 16, 2013 2:19:54 PM UTC-7, Cristiano wrote:

 Hi All

 maybe I can be a little off-topic posting here but this is not an usual 
 user question and hopefully some contributor can help me.

 I want to understand an error that I get in DevMode. The error is the 
 following:

 
 00:00:09,841 [ERROR] Unable to initialize static dispatcher

 java.lang.UnsupportedClassVersionError: 
 com/google/gwt/core/client/JavaScriptObject$ : Unsupported major.minor 
 version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:465)
 at 
 com.google.gwt.dev.shell.CompilingClassLoader.findClass(CompilingClassLoader.java:1121)
 at 
 com.google.gwt.dev.shell.CompilingClassLoader.loadClass(CompilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at com.google.gwt.dev.shell.JsValueGlue.set(JsValueGlue.java:220)
 at 
 com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:129)
 at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:576)
 at 
 com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid(ModuleSpace.java:304)
 at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:347)
 at 
 com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler.java:200)
 at 
 com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:526)
 at 
 com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364)
 at java.lang.Thread.run(Thread.java:680)

 

 I'm not working on the standard release of GWT, I'm running a custom build 
 coming from current GWT development.

 To make things more weird, I'm running the application on a Jetty 7 server 
 (with -noserver option) and debugging with DevMode using the following code 
 snippet:

 String[] newArgs = (-noserver -war target/webapp -startupUrl gwt.html 
+  -logLevel INFO -codeServerPort 9997  
+ net.cristcost.test.gwt.DemoApp).split( ); 
 DevMode.main(newArgs);

 I get that error when I try to open the page with the GWT app in DevMode (
 http://localhost:8080/gwt.html?gwt.codesvr=127.0.0.1:9997)

 With GWT 2.5.1 everything was working, but I had an issue and I needed to 
 exclude org.eclipse.jdt.core dependency from the project due to 
 incompatibility with GWT:  

 dependency 
groupIdorg.eclipse.jetty/groupId 
artifactIdjetty-jsp/artifactId 
version${jetty.version}/version 
scopetest/scope 
!-- This dependency cause issue in GWT compilation in DevMode -- 
exclusions 
   exclusion 
  artifactIdorg.eclipse.jdt.core/artifactId 
  groupIdorg.eclipse.jetty.orbit/groupId 
  /exclusion 
/exclusions 
 /dependency

 (in fact, I am really trying 2.6.0 nightly to see if this problem will 
 persists) 


 Can someone give me some light on the error and explain it? I want to see 
 if I find some workaround.

 Thank you,
 Cristiano




-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.