environments for our application:
- Eclipse 2019-03 with Oracle Java 8u201.
- Eclipse 2020-03 with AdoptOpenJDK 11.0.7.
On Tuesday, April 28, 2020 at 8:02:32 PM UTC-7, Jim Douglas wrote:
>
> My development system here is macOS Catalina; is it helpful to get test
> feedback from
>
>
>
> --
> Colin Alworth
> co...@colinalworth.com
>
>
>
> On Tue, Apr 28, 2020, at 1:02 PM, 'Jim Douglas' via GWT Contributors wrote:
>
> I've got the same build error that Michael reported here, and I'm not sure
> how to get past it.
>
>
.1.0-RC1-sources.jar
> inflating: jsinterop/annotations/Annotations.gwt.xml
> ...
>
>
>
> --
> Colin Alworth
> co...@colinalworth.com
>
>
>
> On Tue, Apr 28, 2020, at 1:02 PM, 'Jim Douglas' via GWT Contributors wrote:
>
> I've got the same build error
I've got the same build error that Michael reported here, and I'm not sure
how to get past it.
I couldn't find a complete self-contained gwt-2.9.0-rc1.zip distribution,
so I hacked one together by downloading 2.8.2 from here:
http://www.gwtproject.org/download.html
I extracted that GWT 2.8.2
Is GPE support still pending? I just did a quick test in Kepler. I set
this as my default GWT SDK, then attempted to GWT Compile my project; it
died immediately with this stack trace:
Compiling module com.basis.bbj.web.gwt.EnglishOnly
[ERROR] Unexpected internal compiler error
, Jim Douglas jdo...@basis.com
javascript: wrote:
Is GPE support still pending? I just did a quick test in Kepler. I set
this as my default GWT SDK, then attempted to GWT Compile my project; it
died immediately with this stack trace:
Compiling module com.basis.bbj.web.gwt.EnglishOnly
:34:40 AM UTC-7, Jim Douglas wrote:
Crap, I knew that, but it's been a few years since it last tripped me up,
so I forgot; retrying now.
On Saturday, October 18, 2014 11:21:23 AM UTC-7, Daniel Kurka wrote:
This looks like an issue with your gwt-unitCache. Can you clear it and
retry
Not trying to run either dev mode, just trying to GWT Compile the package.
On Saturday, October 18, 2014 11:31:44 AM UTC-7, Brandon Donnelson wrote:
There is no special GPE support needed to run GWT 2.7.0-beta1. The same
launch configs can be used.
Although if you want to run dev mode, use
Eureka! (Or not quite, but that was much closer to working.) Apparently
our overall project is dependent on asm-all-3.1.jar, and GWT 2.7.0 has a
newer dependency than GWT 2.6.1 (and the APIs are inompatible). Ok,
swapping in asm-all-5.0.3.jar introduces a flood of build errors in another
Hmm. We do have this in our project.gwt.xml file:
set-configuration-property name='compiler.max.vars.per.var' value='-1'/
I inherited ownership of this project; I'm not sure why that was added.
Removing it does correct that crash. That leaves me with a few
new-for-2.7 linker errors:
Does GWT 2.7 change the default linker behaviour? This configuration works
fine in GWT 2.6.1.
On Saturday, October 18, 2014 3:05:33 PM UTC-7, Jens wrote:
Because ASM 4+ guarantees API compatibility, when we switched to 5.0.3 (to
support Java 8) we decided to use it directly without
, October 19, 2014 12:42:27 AM UTC+2, Jim Douglas wrote:
Does GWT 2.7 change the default linker behaviour? This configuration
works fine in GWT 2.6.1.
On Saturday, October 18, 2014 3:05:33 PM UTC-7, Jens wrote:
Because ASM 4+ guarantees API compatibility, when we switched to 5.0.3
(to support
The folder isn't public (You need permission to access this item.).
On Monday, July 15, 2013 3:38:42 PM UTC-7, Bhaskar Janakiraman wrote:
Hi Folks,
The videos and slides from the GWT Meet-up conference at Google are
finally up. I've uploaded them to a newly created GWT Youtube channel:
Hi Unnur,
This is a regression of code that works in 2.3 and 2.4. But we were able
to implement a workaround based on the suggestions in the bug report.
Jim.
On Thursday, October 25, 2012 5:08:08 PM UTC-7, unnurg wrote:
Hi Adam -
I'm sorry, but we were only considering immediate
Ray,
I didn't submit a formal patch for this, but I noted the trivial fix
in the bug report:
http://code.google.com/p/google-web-toolkit/issues/detail?id=6704
(Not urgent for me; I worked around this when I tripped over it.)
This fix is pending in code review:
FWIW, I noted some touch-related issues here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5148
SplitLayoutPanel is one problem child; another is the ability to drag
dialog windows, because it also assumes the existence of mousemove.
On Oct 26, 8:10 am, Fred Sauer
16 matches
Mail list logo
