[gwt-contrib] Re: Elemental 2 and J2CL timeline

[Paul Stockley]

I am assuming that Google isn't really interested in Widgets and UiBinder 
for J2CL given their usage of GWT in inbox etc. I could be wrong. Assuming 
I am not, I would like to investigate starting up some community projects 
for Widget and Uibinder support. These won't be trivial to replace so we 
will need quite a long lead time. However, I think if we can show the 
community that they will be able to rely on these in the future, it will go 
a long way to reducing the fear that GWT is dead. 


On Wednesday, April 27, 2016 at 10:06:20 AM UTC-4, Colin Alworth wrote:
>
> I can't speak for J2CL's timelines, as it is an internal project at this 
> time. However, it has been stated that it will support GWT's JRE emulation 
> and JsInterop out of the box, and the expectation is that it will simply be 
> a transpiler and won't support generators (suggested that projects move to 
> APT or the like), or linkers (since the Closure Compiler manages this part 
> of things).
>
> By itself, this means that Widget can work, though Element will need to be 
> reimplemented in JsInterop since JSOs won't exist (and JSNI is likely to 
> have a replacement as well). On the other hand, UiBinder uses the GWT 
> Generator system, which doesn't at this time have a clear upgrade path.
>
> To think about life without GWT.create(Foo.class), consider APT-based 
> projects like AutoValue, where class sources are generated on your 
> classpath (by your build tool, and your IDE if configured correctly) so 
> that you can reference these generated classes directly from within your 
> sources. For cases where you want to pick the right implementation (rtl, 
> locale, device formfactor, etc), a factory methods can also be declared 
> within the generated code, and you can reference  that rather than a 
> constructor.
>
> On Tuesday, April 26, 2016 at 8:30:21 AM UTC-5, Paul Stockley wrote:
>>
>> Does anyone have any idea when elemental 2 will be available? Also what 
>> is a rough timeline for a version on J2CL being available, is it 6 months, 
>> a year or more away? 
>>
>> The reason I ask is that I am thinking about how our company can migrate 
>> to the new compiler. We will need widgets and UiBinder for quite a while, 
>> even though we will slowly migrate to React. I was contemplating creating a 
>> project to port the basic Widget framework to use something like elemental. 
>> Also I was thinking about how to build a new version of UiBinder that 
>> didn't use GWT.create.
>>
>

-- 
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/e5cfde32-923a-457d-86db-3de24481af1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

['Daniel Kurka' via GWT Contributors]

With j2cl we do a javac compile up front and thus those basic problems are
gone.

On Wed, Apr 27, 2016 at 4:22 PM Colin Alworth  wrote:

> Agreed - validating supersource is tricky. I've heard of some good options
> lately that change how the project interacts with them (like compiling to
> .class file and leveraging javac to get the errors), but I don't presently
> have any best practices to suggest in general, except tests for each module
> so that you see the failure on a module-by-module basis rather than having
> to disassemble the entire project as it compiles, and using -strict to
> catch uncompilable sources very early.
>
> On Wed, Apr 27, 2016 at 9:12 AM David  wrote:
>
>> Yes the org.w3c stuff was my own, it was defined in the html5 module you
>> see in the classpath.
>> I hope that this was a border case and not typical what happens if you
>> have super sources with import statements that cannot be resolved ?
>> Because in that case the compiler should give a better error message.
>>
>> On Wed, 27 Apr 2016 at 15:50, Colin Alworth  wrote:
>>
>>> Thanks. Can you confirm that org.w3c.dom is your own code, and not part
>>> of GWT, so it was just out of date? I don't see a jar with that name on
>>> your classpath, and neither of the two EntityReference.java files in GWT
>>> live in that package or appear have jsinterop annotations.
>>>
>>>
>>> On Wednesday, April 27, 2016 at 8:46:13 AM UTC-5, stuckagain wrote:
>>>
 Colin,

 The stacktrace was is my initial post.

 Anyway: I managed to find the root cause and solution.

 The super source java file is using JsInterop to map org.w3c.dom API's.
 It had annotations like this:
 @JsType(isNative=true, namespace=JsNamespace.GLOBAL).

 However, in the snapshot this JsNamespace no longer exists and is now
 replaced with JsPackage.GLOBAL.
 After changing those references the compilation now succeeds.

 The old sources were like this:
 package org.w3c.dom;
 import com.google.gwt.core.client.js.JsNamespace;;
 import jsinterop.annotations.JsType;
  @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
 public interface EntityReference extends Node {
 }
 I changed it to this:
 package org.w3c.dom;
 import jsinterop.annotations.JsPackage;
 import jsinterop.annotations.JsType;
  @JsType(isNative=true,namespace=JsPackage.GLOBAL)
 public interface EntityReference extends Node {
 }


 On Wed, 27 Apr 2016 at 15:32, Colin Alworth  wrote:

>>> Can you share the stack trace, the file it is attempting to read, and
> your classpath? It does sound like it might be a bug, but without the
> ability to reproduce, it is difficult to say more. One case where it might
> not be a bug despite its behavior: where it is reusing gwt-unitCache or 
> the
> like from an older version of gwt.
>
> On Wed, Apr 27, 2016 at 8:23 AM David  wrote:
>
 I managed to get this to run in a Debugger, from within the maven
>> invocation.
>> The exception is thrown on a super source file in one of my gwt-lib
>> maven artifacts.
>> It is trying to parse a .java file as a class file and this throws
>> the reported exception.
>>
>> This sounds like a bug to me!?
>>
>> On Wed, 27 Apr 2016 at 14:41, David  wrote:
>>
> It was working fine with GWT 2.8.0-beta1 using the exact same pom
>>> files. When I point to GWT-2.8.0-SNAPSHOT I get this error.
>>> So the only thing that changed is the version of GWT moving from
>>> beta1 to SNAPSHOT.
>>>
>>> I am using logLevel ALL but it looks like the 2.8 compiler does not
>>> really use logging. Besides a few INFO and WARNING statements nothing is
>>> logged
>>>
>>> This is the path that is being used.
>>>
>>> [DEBUG]   (s) projectArtifactMap =
>>> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
>>> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
>>> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
>>> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
>>> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
>>> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
>>> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
>>> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
>>> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
>>> 

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[Colin Alworth]

Agreed - validating supersource is tricky. I've heard of some good options
lately that change how the project interacts with them (like compiling to
.class file and leveraging javac to get the errors), but I don't presently
have any best practices to suggest in general, except tests for each module
so that you see the failure on a module-by-module basis rather than having
to disassemble the entire project as it compiles, and using -strict to
catch uncompilable sources very early.

On Wed, Apr 27, 2016 at 9:12 AM David  wrote:

> Yes the org.w3c stuff was my own, it was defined in the html5 module you
> see in the classpath.
> I hope that this was a border case and not typical what happens if you
> have super sources with import statements that cannot be resolved ?
> Because in that case the compiler should give a better error message.
>
> On Wed, 27 Apr 2016 at 15:50, Colin Alworth  wrote:
>
>> Thanks. Can you confirm that org.w3c.dom is your own code, and not part
>> of GWT, so it was just out of date? I don't see a jar with that name on
>> your classpath, and neither of the two EntityReference.java files in GWT
>> live in that package or appear have jsinterop annotations.
>>
>>
>> On Wednesday, April 27, 2016 at 8:46:13 AM UTC-5, stuckagain wrote:
>>
>>> Colin,
>>>
>>> The stacktrace was is my initial post.
>>>
>>> Anyway: I managed to find the root cause and solution.
>>>
>>> The super source java file is using JsInterop to map org.w3c.dom API's.
>>> It had annotations like this:
>>> @JsType(isNative=true, namespace=JsNamespace.GLOBAL).
>>>
>>> However, in the snapshot this JsNamespace no longer exists and is now
>>> replaced with JsPackage.GLOBAL.
>>> After changing those references the compilation now succeeds.
>>>
>>> The old sources were like this:
>>> package org.w3c.dom;
>>> import com.google.gwt.core.client.js.JsNamespace;;
>>> import jsinterop.annotations.JsType;
>>>  @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
>>> public interface EntityReference extends Node {
>>> }
>>> I changed it to this:
>>> package org.w3c.dom;
>>> import jsinterop.annotations.JsPackage;
>>> import jsinterop.annotations.JsType;
>>>  @JsType(isNative=true,namespace=JsPackage.GLOBAL)
>>> public interface EntityReference extends Node {
>>> }
>>>
>>>
>>> On Wed, 27 Apr 2016 at 15:32, Colin Alworth  wrote:
>>>
>> Can you share the stack trace, the file it is attempting to read, and
 your classpath? It does sound like it might be a bug, but without the
 ability to reproduce, it is difficult to say more. One case where it might
 not be a bug despite its behavior: where it is reusing gwt-unitCache or the
 like from an older version of gwt.

 On Wed, Apr 27, 2016 at 8:23 AM David  wrote:

>>> I managed to get this to run in a Debugger, from within the maven
> invocation.
> The exception is thrown on a super source file in one of my gwt-lib
> maven artifacts.
> It is trying to parse a .java file as a class file and this throws the
> reported exception.
>
> This sounds like a bug to me!?
>
> On Wed, 27 Apr 2016 at 14:41, David  wrote:
>
 It was working fine with GWT 2.8.0-beta1 using the exact same pom
>> files. When I point to GWT-2.8.0-SNAPSHOT I get this error.
>> So the only thing that changed is the version of GWT moving from
>> beta1 to SNAPSHOT.
>>
>> I am using logLevel ALL but it looks like the 2.8 compiler does not
>> really use logging. Besides a few INFO and WARNING statements nothing is
>> logged
>>
>> This is the path that is being used.
>>
>> [DEBUG]   (s) projectArtifactMap =
>> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
>> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
>> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
>> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
>> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
>> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
>> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
>> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
>> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
>> 

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[David]

Yes the org.w3c stuff was my own, it was defined in the html5 module you
see in the classpath.
I hope that this was a border case and not typical what happens if you have
super sources with import statements that cannot be resolved ?
Because in that case the compiler should give a better error message.

On Wed, 27 Apr 2016 at 15:50, Colin Alworth  wrote:

> Thanks. Can you confirm that org.w3c.dom is your own code, and not part
> of GWT, so it was just out of date? I don't see a jar with that name on
> your classpath, and neither of the two EntityReference.java files in GWT
> live in that package or appear have jsinterop annotations.
>
>
> On Wednesday, April 27, 2016 at 8:46:13 AM UTC-5, stuckagain wrote:
>
>> Colin,
>>
>> The stacktrace was is my initial post.
>>
>> Anyway: I managed to find the root cause and solution.
>>
>> The super source java file is using JsInterop to map org.w3c.dom API's.
>> It had annotations like this:
>> @JsType(isNative=true, namespace=JsNamespace.GLOBAL).
>>
>> However, in the snapshot this JsNamespace no longer exists and is now
>> replaced with JsPackage.GLOBAL.
>> After changing those references the compilation now succeeds.
>>
>> The old sources were like this:
>> package org.w3c.dom;
>> import com.google.gwt.core.client.js.JsNamespace;;
>> import jsinterop.annotations.JsType;
>>  @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
>> public interface EntityReference extends Node {
>> }
>> I changed it to this:
>> package org.w3c.dom;
>> import jsinterop.annotations.JsPackage;
>> import jsinterop.annotations.JsType;
>>  @JsType(isNative=true,namespace=JsPackage.GLOBAL)
>> public interface EntityReference extends Node {
>> }
>>
>>
>> On Wed, 27 Apr 2016 at 15:32, Colin Alworth  wrote:
>>
> Can you share the stack trace, the file it is attempting to read, and your
>>> classpath? It does sound like it might be a bug, but without the ability to
>>> reproduce, it is difficult to say more. One case where it might not be a
>>> bug despite its behavior: where it is reusing gwt-unitCache or the like
>>> from an older version of gwt.
>>>
>>> On Wed, Apr 27, 2016 at 8:23 AM David  wrote:
>>>
>> I managed to get this to run in a Debugger, from within the maven
 invocation.
 The exception is thrown on a super source file in one of my gwt-lib
 maven artifacts.
 It is trying to parse a .java file as a class file and this throws the
 reported exception.

 This sounds like a bug to me!?

 On Wed, 27 Apr 2016 at 14:41, David  wrote:

>>> It was working fine with GWT 2.8.0-beta1 using the exact same pom files.
> When I point to GWT-2.8.0-SNAPSHOT I get this error.
> So the only thing that changed is the version of GWT moving from beta1
> to SNAPSHOT.
>
> I am using logLevel ALL but it looks like the 2.8 compiler does not
> really use logging. Besides a few INFO and WARNING statements nothing is
> logged
>
> This is the path that is being used.
>
> [DEBUG]   (s) projectArtifactMap =
> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-webapp=org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-xml=org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-servlet=org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-security=org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-servlets=org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-continuation=org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:compile,
> 

[gwt-contrib] Re: Elemental 2 and J2CL timeline

[Colin Alworth]

I can't speak for J2CL's timelines, as it is an internal project at this 
time. However, it has been stated that it will support GWT's JRE emulation 
and JsInterop out of the box, and the expectation is that it will simply be 
a transpiler and won't support generators (suggested that projects move to 
APT or the like), or linkers (since the Closure Compiler manages this part 
of things).

By itself, this means that Widget can work, though Element will need to be 
reimplemented in JsInterop since JSOs won't exist (and JSNI is likely to 
have a replacement as well). On the other hand, UiBinder uses the GWT 
Generator system, which doesn't at this time have a clear upgrade path.

To think about life without GWT.create(Foo.class), consider APT-based 
projects like AutoValue, where class sources are generated on your 
classpath (by your build tool, and your IDE if configured correctly) so 
that you can reference these generated classes directly from within your 
sources. For cases where you want to pick the right implementation (rtl, 
locale, device formfactor, etc), a factory methods can also be declared 
within the generated code, and you can reference  that rather than a 
constructor.

On Tuesday, April 26, 2016 at 8:30:21 AM UTC-5, Paul Stockley wrote:
>
> Does anyone have any idea when elemental 2 will be available? Also what is 
> a rough timeline for a version on J2CL being available, is it 6 months, a 
> year or more away? 
>
> The reason I ask is that I am thinking about how our company can migrate 
> to the new compiler. We will need widgets and UiBinder for quite a while, 
> even though we will slowly migrate to React. I was contemplating creating a 
> project to port the basic Widget framework to use something like elemental. 
> Also I was thinking about how to build a new version of UiBinder that 
> didn't use GWT.create.
>

-- 
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/1ed4989b-4676-48fb-9450-1e867c5b476c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[Colin Alworth]

Thanks. Can you confirm that org.w3c.dom is your own code, and not part of 
GWT, so it was just out of date? I don't see a jar with that name on your 
classpath, and neither of the two EntityReference.java files in GWT live in 
that package or appear have jsinterop annotations.

On Wednesday, April 27, 2016 at 8:46:13 AM UTC-5, stuckagain wrote:
>
> Colin,
>
> The stacktrace was is my initial post.
>
> Anyway: I managed to find the root cause and solution.
>
> The super source java file is using JsInterop to map org.w3c.dom API's.
> It had annotations like this:
> @JsType(isNative=true, namespace=JsNamespace.GLOBAL).
>
> However, in the snapshot this JsNamespace no longer exists and is now 
> replaced with JsPackage.GLOBAL.
> After changing those references the compilation now succeeds.
>
> The old sources were like this:
> package org.w3c.dom;
> import com.google.gwt.core.client.js.JsNamespace;;
> import jsinterop.annotations.JsType;
>  @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
> public interface EntityReference extends Node {
> }
> I changed it to this:
> package org.w3c.dom;
> import jsinterop.annotations.JsPackage;
> import jsinterop.annotations.JsType;
>  @JsType(isNative=true,namespace=JsPackage.GLOBAL)
> public interface EntityReference extends Node {
> }
>  
>
> On Wed, 27 Apr 2016 at 15:32, Colin Alworth  > wrote:
>
>> Can you share the stack trace, the file it is attempting to read, and 
>> your classpath? It does sound like it might be a bug, but without the 
>> ability to reproduce, it is difficult to say more. One case where it might 
>> not be a bug despite its behavior: where it is reusing gwt-unitCache or the 
>> like from an older version of gwt.
>>
>> On Wed, Apr 27, 2016 at 8:23 AM David  
>> wrote:
>>
>>> I managed to get this to run in a Debugger, from within the maven 
>>> invocation.
>>> The exception is thrown on a super source file in one of my gwt-lib 
>>> maven artifacts.
>>> It is trying to parse a .java file as a class file and this throws the 
>>> reported exception.
>>>
>>> This sounds like a bug to me!?
>>>
>>> On Wed, 27 Apr 2016 at 14:41, David  
>>> wrote:
>>>
 It was working fine with GWT 2.8.0-beta1 using the exact same pom 
 files. When I point to GWT-2.8.0-SNAPSHOT I get this error.
 So the only thing that changed is the version of GWT moving from beta1 
 to SNAPSHOT.

 I am using logLevel ALL but it looks like the 2.8 compiler does not 
 really use logging. Besides a few INFO and WARNING statements nothing is 
 logged

 This is the path that is being used.

 [DEBUG]   (s) projectArtifactMap = 
 {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
  
 com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
  
 javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
  
 com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile, 
 org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile, 
 org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile, 
 org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile, 
 org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile, 
 org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-webapp=org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-xml=org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-servlet=org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-security=org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-servlets=org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-continuation=org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-http=org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-annotations=org.eclipse.jetty:jetty-annotations:jar:9.2.14.v20151106:compile,
  
 org.eclipse.jetty:jetty-plus=org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:compile,
  
 

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[David]

Colin,

The stacktrace was is my initial post.

Anyway: I managed to find the root cause and solution.

The super source java file is using JsInterop to map org.w3c.dom API's.
It had annotations like this:
@JsType(isNative=true, namespace=JsNamespace.GLOBAL).

However, in the snapshot this JsNamespace no longer exists and is now
replaced with JsPackage.GLOBAL.
After changing those references the compilation now succeeds.

The old sources were like this:
package org.w3c.dom;
import com.google.gwt.core.client.js.JsNamespace;;
import jsinterop.annotations.JsType;
 @JsType(isNative=true,namespace=JsNamespace.GLOBAL)
public interface EntityReference extends Node {
}
I changed it to this:
package org.w3c.dom;
import jsinterop.annotations.JsPackage;
import jsinterop.annotations.JsType;
 @JsType(isNative=true,namespace=JsPackage.GLOBAL)
public interface EntityReference extends Node {
}


On Wed, 27 Apr 2016 at 15:32, Colin Alworth  wrote:

> Can you share the stack trace, the file it is attempting to read, and your
> classpath? It does sound like it might be a bug, but without the ability to
> reproduce, it is difficult to say more. One case where it might not be a
> bug despite its behavior: where it is reusing gwt-unitCache or the like
> from an older version of gwt.
>
> On Wed, Apr 27, 2016 at 8:23 AM David  wrote:
>
>> I managed to get this to run in a Debugger, from within the maven
>> invocation.
>> The exception is thrown on a super source file in one of my gwt-lib maven
>> artifacts.
>> It is trying to parse a .java file as a class file and this throws the
>> reported exception.
>>
>> This sounds like a bug to me!?
>>
>> On Wed, 27 Apr 2016 at 14:41, David  wrote:
>>
>>> It was working fine with GWT 2.8.0-beta1 using the exact same pom files.
>>> When I point to GWT-2.8.0-SNAPSHOT I get this error.
>>> So the only thing that changed is the version of GWT moving from beta1
>>> to SNAPSHOT.
>>>
>>> I am using logLevel ALL but it looks like the 2.8 compiler does not
>>> really use logging. Besides a few INFO and WARNING statements nothing is
>>> logged
>>>
>>> This is the path that is being used.
>>>
>>> [DEBUG]   (s) projectArtifactMap =
>>> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
>>> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
>>> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
>>> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
>>> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
>>> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
>>> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
>>> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
>>> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-webapp=org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-xml=org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-servlet=org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-security=org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-servlets=org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-continuation=org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-http=org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-annotations=org.eclipse.jetty:jetty-annotations:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-plus=org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-jndi=org.eclipse.jetty:jetty-jndi:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:apache-jsp=org.eclipse.jetty:apache-jsp:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty:jetty-server=org.eclipse.jetty:jetty-server:jar:9.2.14.v20151106:compile,
>>> org.eclipse.jetty.toolchain:jetty-schemas=org.eclipse.jetty.toolchain:jetty-schemas:jar:3.1.M0:compile,
>>> javax.servlet:javax.servlet-api=javax.servlet:javax.servlet-api:jar:3.0.1:provided,
>>> org.mortbay.jasper:apache-jsp=org.mortbay.jasper:apache-jsp:jar:8.0.9.M3:compile,
>>> org.mortbay.jasper:apache-el=org.mortbay.jasper:apache-el:jar:8.0.9.M3:compile,
>>> 

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[Colin Alworth]

Can you share the stack trace, the file it is attempting to read, and your
classpath? It does sound like it might be a bug, but without the ability to
reproduce, it is difficult to say more. One case where it might not be a
bug despite its behavior: where it is reusing gwt-unitCache or the like
from an older version of gwt.

On Wed, Apr 27, 2016 at 8:23 AM David  wrote:

> I managed to get this to run in a Debugger, from within the maven
> invocation.
> The exception is thrown on a super source file in one of my gwt-lib maven
> artifacts.
> It is trying to parse a .java file as a class file and this throws the
> reported exception.
>
> This sounds like a bug to me!?
>
> On Wed, 27 Apr 2016 at 14:41, David  wrote:
>
>> It was working fine with GWT 2.8.0-beta1 using the exact same pom files.
>> When I point to GWT-2.8.0-SNAPSHOT I get this error.
>> So the only thing that changed is the version of GWT moving from beta1 to
>> SNAPSHOT.
>>
>> I am using logLevel ALL but it looks like the 2.8 compiler does not
>> really use logging. Besides a few INFO and WARNING statements nothing is
>> logged
>>
>> This is the path that is being used.
>>
>> [DEBUG]   (s) projectArtifactMap =
>> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
>> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
>> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
>> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
>> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
>> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
>> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
>> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
>> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-webapp=org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-xml=org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-servlet=org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-security=org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-servlets=org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-continuation=org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-http=org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-annotations=org.eclipse.jetty:jetty-annotations:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-plus=org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-jndi=org.eclipse.jetty:jetty-jndi:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:apache-jsp=org.eclipse.jetty:apache-jsp:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty:jetty-server=org.eclipse.jetty:jetty-server:jar:9.2.14.v20151106:compile,
>> org.eclipse.jetty.toolchain:jetty-schemas=org.eclipse.jetty.toolchain:jetty-schemas:jar:3.1.M0:compile,
>> javax.servlet:javax.servlet-api=javax.servlet:javax.servlet-api:jar:3.0.1:provided,
>> org.mortbay.jasper:apache-jsp=org.mortbay.jasper:apache-jsp:jar:8.0.9.M3:compile,
>> org.mortbay.jasper:apache-el=org.mortbay.jasper:apache-el:jar:8.0.9.M3:compile,
>> com.google.gwt:gwt-elemental=com.google.gwt:gwt-elemental:jar:2.8.0-SNAPSHOT:compile,
>> com.google.inject:guice=com.google.inject:guice:jar:3.0:compile,
>> javax.inject:javax.inject=javax.inject:javax.inject:jar:1:compile,
>> aopalliance:aopalliance=aopalliance:aopalliance:jar:1.0:compile,
>> com.acme.acmeproduct:gui.html5=com.acme.acmeproduct:gui.html5:gwt-lib:0.0.1-SNAPSHOT:compile,
>> com.acme.acmeproduct:gui.editor=com.acme.acmeproduct:gui.editor:gwt-lib:0.0.1-SNAPSHOT:compile,
>> com.acme.acmecommon:common.core=com.acme.acmecommon:common.core:jar:0.0.1-SNAPSHOT:compile,
>> com.acme.acmecommon:common.config=com.acme.acmecommon:common.config:gwt-lib:0.0.1-SNAPSHOT:compile,
>> com.acme.acmecommon:common.servlet=com.acme.acmecommon:common.servlet:jar:0.0.1-SNAPSHOT:compile,
>> com.fasterxml.jackson.core:jackson-core=com.fasterxml.jackson.core:jackson-core:jar:2.7.3:compile,
>> com.fasterxml.jackson.core:jackson-databind=com.fasterxml.jackson.core:jackson-databind:jar:2.7.3:compile,
>> 

Re: [gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[David]

I managed to get this to run in a Debugger, from within the maven
invocation.
The exception is thrown on a super source file in one of my gwt-lib maven
artifacts.
It is trying to parse a .java file as a class file and this throws the
reported exception.

This sounds like a bug to me!?

On Wed, 27 Apr 2016 at 14:41, David  wrote:

> It was working fine with GWT 2.8.0-beta1 using the exact same pom files.
> When I point to GWT-2.8.0-SNAPSHOT I get this error.
> So the only thing that changed is the version of GWT moving from beta1 to
> SNAPSHOT.
>
> I am using logLevel ALL but it looks like the 2.8 compiler does not really
> use logging. Besides a few INFO and WARNING statements nothing is logged
>
> This is the path that is being used.
>
> [DEBUG]   (s) projectArtifactMap =
> {com.google.gwt:gwt-user=com.google.gwt:gwt-user:jar:2.8.0-SNAPSHOT:compile,
> com.google.jsinterop:jsinterop-annotations=com.google.jsinterop:jsinterop-annotations:jar:sources:1.0.0-SNAPSHOT:compile,
> javax.validation:validation-api=javax.validation:validation-api:jar:sources:1.0.0.GA:compile,
> com.google.gwt:gwt-dev=com.google.gwt:gwt-dev:jar:2.8.0-SNAPSHOT:compile,
> org.ow2.asm:asm=org.ow2.asm:asm:jar:5.0.3:compile,
> org.ow2.asm:asm-util=org.ow2.asm:asm-util:jar:5.0.3:compile,
> org.ow2.asm:asm-tree=org.ow2.asm:asm-tree:jar:5.0.3:compile,
> org.ow2.asm:asm-commons=org.ow2.asm:asm-commons:jar:5.0.3:compile,
> org.eclipse.jetty.websocket:websocket-client=org.eclipse.jetty.websocket:websocket-client:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-util=org.eclipse.jetty:jetty-util:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-io=org.eclipse.jetty:jetty-io:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty.websocket:websocket-common=org.eclipse.jetty.websocket:websocket-common:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty.websocket:websocket-api=org.eclipse.jetty.websocket:websocket-api:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-webapp=org.eclipse.jetty:jetty-webapp:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-xml=org.eclipse.jetty:jetty-xml:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-servlet=org.eclipse.jetty:jetty-servlet:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-security=org.eclipse.jetty:jetty-security:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-servlets=org.eclipse.jetty:jetty-servlets:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-continuation=org.eclipse.jetty:jetty-continuation:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-http=org.eclipse.jetty:jetty-http:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-annotations=org.eclipse.jetty:jetty-annotations:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-plus=org.eclipse.jetty:jetty-plus:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-jndi=org.eclipse.jetty:jetty-jndi:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:apache-jsp=org.eclipse.jetty:apache-jsp:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty:jetty-server=org.eclipse.jetty:jetty-server:jar:9.2.14.v20151106:compile,
> org.eclipse.jetty.toolchain:jetty-schemas=org.eclipse.jetty.toolchain:jetty-schemas:jar:3.1.M0:compile,
> javax.servlet:javax.servlet-api=javax.servlet:javax.servlet-api:jar:3.0.1:provided,
> org.mortbay.jasper:apache-jsp=org.mortbay.jasper:apache-jsp:jar:8.0.9.M3:compile,
> org.mortbay.jasper:apache-el=org.mortbay.jasper:apache-el:jar:8.0.9.M3:compile,
> com.google.gwt:gwt-elemental=com.google.gwt:gwt-elemental:jar:2.8.0-SNAPSHOT:compile,
> com.google.inject:guice=com.google.inject:guice:jar:3.0:compile,
> javax.inject:javax.inject=javax.inject:javax.inject:jar:1:compile,
> aopalliance:aopalliance=aopalliance:aopalliance:jar:1.0:compile,
> com.acme.acmeproduct:gui.html5=com.acme.acmeproduct:gui.html5:gwt-lib:0.0.1-SNAPSHOT:compile,
> com.acme.acmeproduct:gui.editor=com.acme.acmeproduct:gui.editor:gwt-lib:0.0.1-SNAPSHOT:compile,
> com.acme.acmecommon:common.core=com.acme.acmecommon:common.core:jar:0.0.1-SNAPSHOT:compile,
> com.acme.acmecommon:common.config=com.acme.acmecommon:common.config:gwt-lib:0.0.1-SNAPSHOT:compile,
> com.acme.acmecommon:common.servlet=com.acme.acmecommon:common.servlet:jar:0.0.1-SNAPSHOT:compile,
> com.fasterxml.jackson.core:jackson-core=com.fasterxml.jackson.core:jackson-core:jar:2.7.3:compile,
> com.fasterxml.jackson.core:jackson-databind=com.fasterxml.jackson.core:jackson-databind:jar:2.7.3:compile,
> com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider=com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.6.3:compile,
> com.fasterxml.jackson.jaxrs:jackson-jaxrs-base=com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:jar:2.6.3:compile,
> com.fasterxml.jackson.module:jackson-module-jaxb-annotations=com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.3:compile,
> com.fasterxml.jackson.core:jackson-annotations=com.fasterxml.jackson.core:jackson-annotations:jar:sources:2.7.2:provided,
> 

[gwt-contrib] Re: GWT 2.8.0 SNAPSHOT compiler crash

[Jens]

Hmm never seen this. Maybe some ASM 3.x has creeped into your classpath? 
GWT 2.8 requires ASM 5.x.

-- 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/00a4b8ad-8d94-42d2-ab49-47a7852fa1b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8.0 SNAPSHOT compiler crash

[stuckagain]

Nobody as this problem ?

-- 
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/dffde24b-cb4c-417e-a3f5-27e3ba6f0b79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.