[gwt-contrib] Re: Unable to compile GWT 2.8.0-rc1 module in IntelliJ

Hi, Finally, after couple hours, I found out that there was a conflict in apache-ant dependency. Multiple packages with different versions served the same stuff. I hope this might help others to solve this kind of issue. m. Dňa pondelok, 30. marca 2020 11:34:13 UTC+2 Michal Zimen

[gwt-contrib] Re: Unable to compile GWT 2.8.0-rc1 module in IntelliJ

Hi, I'm facing similar problem. Migrating from gwt-2.4.0 to gwt-2.8.2 along with jdk1.6 migration to jdk1.8. I've added the gwt-dev-2.8.2 dependency to the classpath/refid to the below construct, but the issue still persists. This is a part of the error message: [java]

Re: Best server and Java version for implementing GWT 2.8.0.

; I want to use most of the features, that GWT 2.8.0 can offer. I wonder >> which server should I use, from the comparison chart below. >> >> http://tomee.apache.org/comparison.html >> > > GWT's server-side parts (GWT-RPC or RequestFactory) only need Java > Servlets

Re: Best server and Java version for implementing GWT 2.8.0.

On Tuesday, January 8, 2019 at 5:30:05 PM UTC+1, Zetha Nath wrote: > > Hi there, > > I want to use most of the features, that GWT 2.8.0 can offer. I wonder > which server should I use, from the comparison chart below. > > http://tomee.apache.org/comparison.html > GWT'

Best server and Java version for implementing GWT 2.8.0.

Hi there, I want to use most of the features, that GWT 2.8.0 can offer. I wonder which server should I use, from the comparison chart below. http://tomee.apache.org/comparison.html Also, GWT 2.8.0 works best on Java 8 correct? Thank you so much. -- You received this message because you

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

Yesss, the above solution worked. Luckily it was the only construction I had, I only had to rewrite this one. Sorry, there will not be any upgrade to 3.0 -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

> BTW: what is the correct way to solve this? > > Should I make a new class that extends both JavaScriptObject and > implements ZtoeslagAppConfig? > Yes, and getPages() would be implemented using JSNI. That also means that AppPage should be a JSO (and might implement in interface).

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

BTW: what is the correct way to solve this? Should I make a new class that extends both JavaScriptObject and implements ZtoeslagAppConfig? So it would be: SimpleZtoeslagAppConfig extends JavaScriptObject implements ZtoeslagAppConfig { } *private* SimpleZtoeslagAppConfig getZtoeslagConfig() {

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

Thanks for the inside Jens, I think that could be it, I will test it. Ed -- 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

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

Hmm as you are using intersection types this might be related to https://github.com/gwtproject/gwt/commit/1ce1c710c7d3d7bffc246c7f013009b670be44a4 which has been committed between 2.8.0 and 2.8.2. So it could very well be that now there is a cast check inserted by GWT because you use an

Re: A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

Anybody any idea please? -- 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

A class cast exception when upgrading from GWT 2.8.0 to 2.8.2 ?

I just upgraded from GWT 2.8.0 to 2.8.2 and get a class cast exception which I don't understand, please some help. It goes wrong in the following line of code: *ZtoeslagAppConfig this.bla = new JsoZtoeslagAppConfig(getZtoeslagConfig());* All relevant code: *private T getZtoeslagConfig

Development Mode - Jetty - Realm - Redirecting to 403 - Forbidden page - GWT - 2.8.0

Is this right place to discuss about my issue ? Just raised in Github. Please help. Its urgent. Thanks. https://github.com/gwtproject/gwt/issues/9589 -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Re: GWT 2.8.0 RC2 is here!

Have a look at https://github.com/gwtproject/gwt/tree/master/samples/mobilewebapp, we haven't had issues with AppEngine and GWT in the same Maven module (even though I discourage such usage). On Friday, July 21, 2017 at 10:47:41 AM UTC+2, Patrick Tessier wrote: > > I'm upgrading from 2.7 to

Re: GWT 2.8.0 RC2 is here!

I'm upgrading from 2.7 to 2.8.1 now, but it seems I'm running into the same issue as Tony. I'm using AppEngine on the server side, which is in the same IntelliJ/Maven module as the GWT code. When launching devmode from IntelliJ, I get "Couldn't load project from Super Dev Mode server at...",

Re: GWT 2.8.0 Eclipse

GPE is deprecated and will no longer continuing support for GWT. The features have been split between the GWT Eclipse Plugin and Google Cloud Tools Plugin for Eclipse. The older versions of GPE still work, but not recommended. http://gwt-plugins.github.io/documentation/ - GWT Eclipse Plugin On

Re: GWT 2.8.0 Eclipse

The standard plugin for eclipse neon available at https://dl.google.com/eclipse/plugin/4.6 works fine with GWT 2.8 Regards, Rodolfo On Fri, Feb 17, 2017 at 1:45 PM wrote: > Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was released > like half a year ago.

Re: GWT 2.8.0 Eclipse

I switched without problems (I didn't update anything in eclipse) On Thu, 23 Feb 2017 at 08:19 prashant fulara wrote: > Given link (https://github.com/gwt-plugins/gwt-eclipse-plugin >

Re: GWT 2.8.0 Eclipse

Given link (https://github.com/gwt-plugins/gwt-eclipse-plugin ), seems not opening. On Saturday, 18 February 2017 02:32:33 UTC+5:30, Slava Pankov wrote: > > This one

Re: GWT 2.8.0 Eclipse

We are currently working with GWT 2.7 using eclipse and planning to switch to GWT 2.8 in near future. How safe it is to switch to GWT 2.8 (using Eclipse as IDE) ? On Tuesday, 21 February 2017 23:38:54 UTC+5:30, Brandon Donnelson wrote: > > I plan on adding more patches and enhancements this

Re: GWT 2.8.0 Eclipse

I plan on adding more patches and enhancements this year to the plugin. On Friday, February 17, 2017 at 1:02:33 PM UTC-8, Slava Pankov wrote: > > This one works with GWT 2.8 perfectly: > http://storage.googleapis.com/gwt-eclipse-plugin/v3/release > > Sources are here:

Re: GWT 2.8.0 Eclipse

This one works with GWT 2.8 perfectly: http://storage.googleapis.com/gwt-eclipse-plugin/v3/release Sources are here: https://github.com/gwt-plugins/gwt-eclipse-plugin On Friday, February 17, 2017 at 8:45:25 AM UTC-8, l.s...@behaimits.com wrote: > > Hi, I have noticed that GWT 2.7 is 3 years

GWT 2.8.0 Eclipse

Hi, I have noticed that GWT 2.7 is 3 years old. GWT 2.8 final was released like half a year ago. How should one develop GWT applications - in which IDE? Will there be an update for GWT Eclipse plugin this year? -- You received this message because you are subscribed to the Google Groups "GWT

Re: compiler errors after upgrade to gwt 2.8.0

The plugin is actually included out of box in eclipse. You can try by downloading eclipse neon or reinstall the plugin in mars El vie., 17 de feb. de 2017 01:09, Magnus escribió: > Hello Juan, > > ok, I understand that eclipse:eclipse is retired. > > I installed

Re: compiler errors after upgrade to gwt 2.8.0

Hello Juan, ok, I understand that eclipse:eclipse is retired. I installed m2eclipse from the repository site, but after that there is nothing about "maven" in the eclipse menus. Even the option "Import existing maven projects" is gone! Even after uninstalling m2eclipse the option didn't come

Re: compiler errors after upgrade to gwt 2.8.0

Hello Juan! On Thursday, February 16, 2017 at 7:38:04 PM UTC+1, Juan Pablo Gardella wrote: > > Check http://maven.apache.org/plugins/maven-eclipse-plugin > Ok, I understand that eclipse:eclipse is retired. So I'll switch to m2e. However, do I have to "clean up" my maven project first, u. e.

Re: compiler errors after upgrade to gwt 2.8.0

Check http://maven.apache.org/plugins/maven-eclipse-plugin/ On Thu, 16 Feb 2017 at 15:24 Magnus wrote: > Hello Juan, > > sorry, it seems that I didn't point out that my problem is solved! > > After executing "mvn eclipse:eclipse" the errors are gone! > So what's wrong

Re: compiler errors after upgrade to gwt 2.8.0

Hello Juan, sorry, it seems that I didn't point out that my problem is solved! After executing "mvn eclipse:eclipse" the errors are gone! So what's wrong with "eclipse:eclipse" then? Thanks Magnus -- You received this message because you are subscribed to the Google Groups "GWT Users"

Re: compiler errors after upgrade to gwt 2.8.0

I suggest the following: 1) Copy src/ + pom.xml file to another directory. (or remove the project from the eclipse and delete eclipse related files). 2) Import the project again. Do not use *mvn eclipse:eclipse, *it's better to use m2e plugin. Let me know also if mvn clean package works (execute

Re: compiler errors after upgrade to gwt 2.8.0

Hello, I found that the .classpath file in the root directory of my maven library project contains a reference to gwt 2.7.0:

Re: compiler errors after upgrade to gwt 2.8.0

; As soon as I add my library project to the build path, the compilation > error occurrs! So the error must be caused by this library project. > > The library project is a maven project with server-side and client-side > (GWT) code. I upgraded it to GWT 2.8.0 by editing the pom.xml and exec

Re: compiler errors after upgrade to gwt 2.8.0

rary project is a maven project with server-side and client-side > (GWT) code. I upgraded it to GWT 2.8.0 by editing the pom.xml and executing > "mvn package". > Where should I look next? > > Thanks > > Magnus > > -- > You received this message because you are

Re: compiler errors after upgrade to gwt 2.8.0

library project. The library project is a maven project with server-side and client-side (GWT) code. I upgraded it to GWT 2.8.0 by editing the pom.xml and executing "mvn package". Where should I look next? Thanks Magnus -- You received this message because you are subscribed to the

Re: compiler errors after upgrade to gwt 2.8.0

). On Thursday, February 16, 2017 at 6:23:28 AM UTC+1, Magnus wrote: > > Hello, > > after upgrading a project from GWT 2.7.0 to GWT 2.8.0 I and when compiling > with the GWT compiler using the -strict option, I get a lot of errors like > this: > >Tracing compi

compiler errors after upgrade to gwt 2.8.0

Hello, after upgrading a project from GWT 2.7.0 to GWT 2.8.0 I and when compiling with the GWT compiler using the -strict option, I get a lot of errors like this: Tracing compile failure path for type 'java.util.stream.Stream' [ERROR] Errors in 'jar:file:/home/magnus/dvl/lib/gwt

Re: GWT 2.8.0 released

This depends on amount of code and permutations you build. -- 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

Re: GWT 2.8.0 released

I noticed that I had to increase the Max heap size a lot when compiling through the gwt-maven-plugin. I increased it from 1G to 2G to not getting the exception "GC overhead limit exceeded". What is your experience with this? What are the recommended settings when using java 8? (like GC method,

Re: GWT 2.8.0 released

sLoader.defineClass(SecureClassLoader.java:124) >> at >> weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:344) >> at >> weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:301) >> Trun

Re: GWT 2.8.0 released

GWT 2.8 dropped support for Java 6. You can probably use tools to "backport" the JAR to be Java 6-compatible. -- 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

Re: GWT 2.8.0 released

alClass(GenericClassLoader.java:301) > Truncated. see log file for complete stacktrace > > > > > > > On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: >> >> Hi all, >> >> I am very happy to announce GWT 2.8.0 on behalf o

Re: GWT 2.8.0 released

your help. On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/dow

Re: GWT 2.8.0 compile warnings

Perfect, thankyou very much On Thursday, December 8, 2016 at 6:09:00 PM UTC, Dave Kichler wrote: > > The GWT 8 gwt-user jar (com.google.gwt:gwt-user:2.8.0) has a dependency on > jsinterop 1.0.1. The problem is Ivy fails to properly download that > transitive dependency (grabs only the

Re: GWT 2.8.0 compile warnings

+1 to Dave's answer Here is the relevant bug https://issues.apache.org/jira/browse/IVY-1003 On Thu, Dec 8, 2016 at 8:09 PM, Dave Kichler wrote: > The GWT 8 gwt-user jar (com.google.gwt:gwt-user:2.8.0) has a dependency > on jsinterop 1.0.1. The problem is Ivy fails to

Re: GWT 2.8.0 compile warnings

The GWT 8 gwt-user jar (com.google.gwt:gwt-user:2.8.0) has a dependency on jsinterop 1.0.1. The problem is Ivy fails to properly download that transitive dependency (grabs only the sources). By adding an explicit dependency on jsinterop, and telling Ivy explicitly to download both binaries

Re: GWT 2.8.0 compile warnings

Hi Dave, how did you resolve this? I'm not deeply familiar with Ivy, so feeling a bit out of my depth. Adding an explicit dependency on jsinterop to my ivy.xml file seems to have no effect at my end, so long as gwt-user is in there too it overrides my classifier :\ If i take gwt-user out

Re: GWT 2.8.0 released

Hi Daniel, I am using GWT 2.8.0 and using -generateJsInteropExports with Polymer to access GWT elements, however I was able to get it successfully with 2.8 RC2 but getting error with 2.8 final version, gwt-elements.html:72 Uncaught ReferenceError: com is not defined(…)attached @ gwt

Re: GWT 2.8.0 compile warnings

Eventually figured out that the GWT jars downloaded from Google have the jsinterop annotations bundled within the gwt-user.jar, which are the ones referenced by Eclipse and the ones I checked for them. The GWT jars provided by Maven central, and which my Ant/Ivy build were referencing, do not

Re: GWT 2.8.0 compile warnings

Scoured my classpath for any conflicting dependencies and found none. Also cleared out my gwt-unitCache but no to avail - the warnings still remain. On Wednesday, 23 November 2016 13:13:23 UTC-8, Jens wrote: > > Double check your classpath. Especially if you use gradle/maven make sure > you

Re: GWT 2.8.0 compile warnings

On Thursday, November 24, 2016 at 12:13:23 AM UTC+3, Jens wrote: > > Also try deleting your gwt-unitCache. > This helps for our case many times per day. Even more we have a special single-button-task in IDEA that clears all gwt-unitCache(es) and this really helps in compilation and

Re: GWT 2.8.0 compile warnings

Double check your classpath. Especially if you use gradle/maven make sure you really have only a single GWT version on classpath. Also try deleting your gwt-unitCache. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from

GWT 2.8.0 compile warnings

I recently upgraded my GWT app to depend on 2.8.0 and had my compile phase immediately flooded with GWT compile warnings. Under previous versions, there were no warnings at all. I've done some Googling but haven't found a solution to this particular issue. Some other similar issues

Re: Internal GWT 2.8.0 compiler exception

Yes, that was it. lib-gwt-svg was the wrong version. Thank you for the pointer! jay On Wednesday, November 16, 2016 at 9:41:13 AM UTC-8, jgindin wrote: > > I'm trying to update my project from GWT 2.7.0 to 2.8.0. However, I'm > getting the following error during the GWT compilation. > > We're

Re: Internal GWT 2.8.0 compiler exception

Caused by: java.lang.NoSuchMethodError: com.google.gwt.uibinder.rebind. UiBinderWriter.(Lcom/google/gwt/core/ext/typeinfo/JClassType;Ljava/ lang/String;Ljava/lang/String;Lcom/google/gwt/core/ext/typeinfo/TypeOracle; Lcom/google/gwt/uibinder/rebind/MortalLogger;Lcom/google/gwt/uibinder/rebind

Re: Internal GWT 2.8.0 compiler exception

Have you tried increasing the allocated ram? On 11/16/2016 12:41 PM, jgindin wrote: I'm trying to update my project from GWT 2.7.0 to 2.8.0. However, I'm getting the following error during the GWT compilation. We're using dagger and guava 20. I've validated that: * dagger-compiler is

Internal GWT 2.8.0 compiler exception

I'm trying to update my project from GWT 2.7.0 to 2.8.0. However, I'm getting the following error during the GWT compilation. We're using dagger and guava 20. I've validated that: - dagger-compiler is *NOT* in the classpath when compiling. (We're using gradle and the "net.ltgt.apt"

Re: GWT 2.8.0 released

1.jar jars, which can be found at >> https://mvnrepository.com/artifact/com.google.jsinterop/jsinterop-annotations, >> >> only contain the binaries. >> >> Please let me know if this is not the correct "forum" for this question. >> >> Best reg

Re: GWT 2.8.0 released

op/jsinterop-annotations, > > only contain the binaries. > > Please let me know if this is not the correct "forum" for this question. > > Best regards > Rasmus > > > Den fredag den 21. oktober 2016 kl. 21.21.41 UTC+2 skrev Daniel Kurka: >> >> Hi al

Re: GWT 2.8.0 released

/com.google.jsinterop/jsinterop-annotations, only contain the binaries. Please let me know if this is not the correct "forum" for this question. Best regards Rasmus Den fredag den 21. oktober 2016 kl. 21.21.41 UTC+2 skrev Daniel Kurka: > > Hi all, > > I am very happy to announ

Re: GWT 2.8.0 released

Thomas, Finally, i was able to make superdev mode work. I had to exclude all the jetty 8.1 dependencies (those were getting included because of my some other internal dependency). In addition to that, i am also now using 3.1 servlet-api version (it was 3.0.1). Thanks again. Appreciated.

Re: GWT 2.8.0 released

Thanks Thomas for your reply. You are correct, we definitely needs to optimize these dependencies. About this 'AggregateLifeCycle class. ' Issue. I did able to find out the origin of jetty-deploy from where it was coming, but even excluding it doesn't solve my issue. Any other hint , from where

Re: GWT 2.8.0 released

On Monday, November 7, 2016 at 11:17:10 PM UTC+1, Zeeshan Chughtai wrote: > > Hi, > > Thanks for this, really happy to have it around. > > We were using 2.8.0-beta1 version for a while without any major fuss. > > While upgrading to 2.8.0 released version, we get stuck with codeserver >

Re: GWT 2.8.0 released

Hi, Thanks for this, really happy to have it around. We were using 2.8.0-beta1 version for a while without any major fuss. While upgrading to 2.8.0 released version, we get stuck with codeserver refused to start because of class loading issues. Here are the changes which we had to made.

Re: GWT 2.8.0 released

: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/download.html > or from maven central. > > The release notes can be found at >

Re: GWT 2.8.0 is not compatible with java6

Hi Marko, I'm using GWT RPC, so it's required gwt-servlet in the WAR file. As it's deployed in an old Jboss server with java6, by using retrolambda, it's possible to use gwt-servlet 2.8 in the server. Juan On Fri, 4 Nov 2016 at 07:37 Thomas Broyer wrote: > With the

Re: GWT 2.8.0 is not compatible with java6

With the exception of a few corner-cases, Java 6 source code is also Java 8 compliant; so the GWT Compiler should be able to process it even though it assumes Java 8 source code. But the question was about JVM requirements: gwt-servlet.jar is compiled as Java 7 bytecode in 2.8, so it requires

Re: GWT 2.8.0 is not compatible with java6

How can you use retrolambda for that? Isn't retrolambda transforming the compiled >>bytecode<>source code<< and not bytecode... Marko -- 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

Re: GWT 2.8.0 is not compatible with java6

Hi all, A workaround to use gwt-2.8.0 in Java 6 is using retrololamda <https://github.com/orfjackal/retrolambda>. Here how I configured it (using maven), by adding a profile (here the gist <https://gist.github.com/gardellajuanpablo/727d3b53e4e5a92e4068b272aa8b4fed#file-gwt28-usingjav

Re: Closure compiler and GWT 2.8.0

This is also a big issue for me since in my application every Kb matters. Right now this prevent me from migrating to 2.8. Le mercredi 26 octobre 2016 23:21:02 UTC+2, Slava Pankov a écrit : > > Integrated closure compiler was removed in 2.8.0 > So now I'm trying to use external

Re: GWT 2.8.0 is not compatible with java6

On Wednesday, November 2, 2016 at 2:38:38 PM UTC+1, Juan Pablo Gardella wrote: > > Hi all, > > At release notes is not mentioned that now it will support only java7. > Good catch! > I found tbroyer comment here: >

GWT 2.8.0 is not compatible with java6

Hi all, At release notes is not mentioned that now it will support only java7. I found tbroyer comment here: http://stackoverflow.com/questions/28879590/jdk-and-jre-minimal-versions-required-for-gwt-compiling-and-running Can be updated the release notes with that?

Re: GWT 2.8.0 released

The doc/javadoc directory is incomplete. It is missing the index.html and the other files to complete it. Will these be added to the gwt-2.8.0.zip? On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behal

Re: Closure compiler and GWT 2.8.0

On Wednesday, October 26, 2016 at 11:21:02 PM UTC+2, Slava Pankov wrote: > > Integrated closure compiler was removed in 2.8.0 > So now I'm trying to use external (post-processing) call to closure > compiler. > SIMPLE mode is working just fine, but gives no improvement over standard > GWT

Closure compiler and GWT 2.8.0

Integrated closure compiler was removed in 2.8.0 So now I'm trying to use external (post-processing) call to closure compiler. SIMPLE mode is working just fine, but gives no improvement over standard GWT compilation at all. ADVANCED mode gives improvement (when GWT compiled in PRETTY mode), but

Re: GWT 2.8.0 released

great news! thanks to everybody who made this happen! On Saturday, October 22, 2016 at 2:21:41 AM UTC+7, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download

Re: GWT 2.8.0 released

Thank you! Hal Maner M Systems International, Inc. On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download

Re: GWT 2.8.0 released

May read this http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0 The big points are Java8 support, JsInterop (to step away from JSNI), GSS and more performance in SDM and the emulation. -- You received this message because you are subscribed to the Google Groups "GWT Users"

Re: GWT 2.8.0 released

m very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/download.html > or from maven central. > > The release notes can be found at > http://www.gwtproject.org/relea

Re: GWT 2.8.0 released

Cool! So what's next? I see a bunch of unmerged code request sitting in gerrit. Is GWT 2.9 coming with all things in it that did not make it into 2.8? if so, when? On Friday, October 21, 2016 at 12:21:41 PM UTC-7, Daniel Kurka wrote: > > Hi all, > > I am very happy to announ

Re: GWT 2.8.0 released

Yes! Guava 20 requires GWT 2.8 and the other way around. -- 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

Re: GWT 2.8.0 released

> Can someone confirm? are we able to use Guava with this version? 20-rc1? > Yes, 20-rc1 actually requires GWT 2.8 and is incompatible to older GWT releases. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this

Re: GWT 2.8.0 released

Can someone confirm? are we able to use Guava with this version? 20-rc1? On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. >

Re: GWT 2.8.0 released

Thanks! -- 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

Re: GWT 2.8.0 released

On Saturday, October 22, 2016 at 8:31:43 PM UTC+2, zakaria amine wrote: > > Great! Elemental 2 is part of it ? > No. Elemental 2 will be released independently (along with its generator I believe) -- You received this message because you are subscribed to the Google Groups "GWT Users"

Re: GWT 2.8.0 released

The best news in years! Well done to the GWT team! Java8, JsInterop and Elemental2 makes a really big difference in my projects. Looking forward for what's next to come. On Sat, Oct 22, 2016 at 8:31 PM zakaria amine wrote: > Great! Elemental 2 is part of it ? > > -- >

Re: GWT 2.8.0 released

Great! Elemental 2 is part of it ? -- 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

Re: GWT 2.8.0 released

Kudos to Daniel and the GWT team! On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http

Re: GWT 2.8.0 released

Awesome news .. well done! -- 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

GWT 2.8.0 released

Thank you for all the effort. -- 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

Re: GWT 2.8.0 released

Thanks...great job -- 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

Re: GWT 2.8.0 released

Thank You for Your effort! On Fri, Oct 21, 2016 at 4:01 PM, Denis Shagaleev <denis.shagal...@gmail.com> wrote: > yeah!! > > thank you guys! > > > On Friday, October 21, 2016 at 10:21:41 PM UTC+3, Daniel Kurka wrote: >> >> Hi all, >> >> I am very

Re: GWT 2.8.0 released

yeah!! thank you guys! On Friday, October 21, 2016 at 10:21:41 PM UTC+3, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproj

Re: GWT 2.8.0 released

hame. I'm not being negative; this is a >>> team that needs more criticism, both internal and external. >>> >>> >>> On Saturday, October 22, 2016 at 5:21:41 AM UTC+10, Daniel Kurka wrote: >>>> >>>> Hi all, >>>> >>

Re: GWT 2.8.0 released

:21:41 AM UTC+10, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/download.html > or from maven central. > > Th

Re: GWT 2.8.0 released

tproject.org for the release? For shame. I'm not being negative; this > is a team that needs more criticism, both internal and external. > > > On Saturday, October 22, 2016 at 5:21:41 AM UTC+10, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on be

Re: GWT 2.8.0 released

egative; this >> is a team that needs more criticism, both internal and external. >> >> >> On Saturday, October 22, 2016 at 5:21:41 AM UTC+10, Daniel Kurka wrote: >> >> Hi all, >> >> I am very happy to announce GWT 2.8.0 on behalf of the GWT steering >> committ

Re: GWT 2.8.0 released

tproject.org for the release? For shame. I'm not being negative; this > is a team that needs more criticism, both internal and external. > > > On Saturday, October 22, 2016 at 5:21:41 AM UTC+10, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on be

Re: GWT 2.8.0 released

Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/download.html > or from maven central. > > The release notes can be found at >

Re: GWT 2.8.0 released

Cool. Nice Job. We have ported out project and it works perfectly. Thanks -- 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

Re: GWT 2.8.0 released

YEES On 21 October 2016 at 21:48, Wesley.JUNG <wesley.j...@gmail.com> wrote: > Hoorey~~~ > > > On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: >> >> Hi all, >> >> I am very happy to announce GWT 2.8.0 on behalf of the GWT steeri

Re: GWT 2.8.0 released

Hoorey~~~ On Friday, October 21, 2016 at 3:21:41 PM UTC-4, Daniel Kurka wrote: > > Hi all, > > I am very happy to announce GWT 2.8.0 on behalf of the GWT steering > committee and the GWT team at Google. > > You can download the release from http://www.gwtproject.org/dow

  1   2   3   4   >