GWT Future plan
Hi All, We have multiple product developed primarily using GWT and currently used by our end customers. Wanted to know the road map of GWT. I got some unofficial update that google is moving there product which is developed in GWT to some other new technology. Is it true? What is long term plan for GWT and also we haven't seen any new release from past one year. Any suggestions ? -- 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: Happy to announce general access for J2CL!
Thank you! On Tuesday, November 13, 2018 at 5:39:28 PM UTC-8, Goktug Gokdogan wrote: > > Dear GWTers! > > We are happy to announce that we have opened up J2CL repository for > general access: > http://github.com/google/j2cl > > Please see the README for details and instructions. > > I also would like to use this opportunity to thank all Googlers who > contributed over the years and made this happen. > > Enjoy! > > Goktug, on behalf of J2CL team > > PS: If you are using Windows, you might have a bumpy road but should get > better over time with your feedback and contributions. > -- 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: Happy to announce general access for J2CL!
Thanks! On Tue, 13 Nov 2018 at 22:39 'Goktug Gokdogan' via GWT Users < google-web-toolkit@googlegroups.com> wrote: > Dear GWTers! > > We are happy to announce that we have opened up J2CL repository for > general access: > http://github.com/google/j2cl > > Please see the README for details and instructions. > > I also would like to use this opportunity to thank all Googlers who > contributed over the years and made this happen. > > Enjoy! > > Goktug, on behalf of J2CL team > > PS: If you are using Windows, you might have a bumpy road but should get > better over time with your feedback and contributions. > > -- > 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. > -- 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.
[gwt-contrib] Fwd: Happy to announce general access for J2CL!
-- Forwarded message - From: Goktug Gokdogan Date: Tue, Nov 13, 2018 at 5:38 PM Subject: Happy to announce general access for J2CL! To: Dear GWTers! We are happy to announce that we have opened up J2CL repository for general access: http://github.com/google/j2cl Please see the README for details and instructions. I also would like to use this opportunity to thank all Googlers who contributed over the years and made this happen. Enjoy! Goktug, on behalf of J2CL team PS: If you are using Windows, you might have a bumpy road but should get better over time with your feedback and contributions. -- 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/CAN%3DyUA2sBEt4WqPXMU7XBpL8mwpqJPPJtjUv_dF%2B6wh2pMVZ3A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Happy to announce general access for J2CL!
Dear GWTers! We are happy to announce that we have opened up J2CL repository for general access: http://github.com/google/j2cl Please see the README for details and instructions. I also would like to use this opportunity to thank all Googlers who contributed over the years and made this happen. Enjoy! Goktug, on behalf of J2CL team PS: If you are using Windows, you might have a bumpy road but should get better over time with your feedback and contributions. -- 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.
[gwt-contrib] Re: Updating GWT CLDR data from v25 to v32
Hi With the PR for the tools being already merged https://github.com/gwtproject/tools/pull/16 I am looking for review and approval on the gwt PR https://gwt-review.googlesource.com/c/gwt/+/21421 Thanks. On Friday, February 2, 2018 at 9:47:59 PM UTC+2, Ahmad Bawaneh wrote: > > Dears > I have been working on updating the CLDR data from cldr version 25 to cldr > version 32, the generation of the new data have been done successfully and > all gwt test cases pass. > > i would like to make a pull request for both the cldr tools and gwt but > first i need to discuss the part related to the *GoogleMods.patch* > > this patch was supposed to be version 25 which is too old now and since we > are going to a new version of cldr data 32 Do we still need to fix and > apply the patch, or should we go with a more standard cldr data? > > i need to decide on this before i finish my work and make a pull request. > > 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/137af5a8-ae28-44ed-a0ba-bd165df6530c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Deobfuscated stack trace message and line-specific stack traces
Hi, I do not know about version 2.8, but for 2.6 we did next: - put value "PRETTY" in the pom.xml for gwt plugin - put next loggin settings in the application gwt config file as result we had a proper class names and line numbers in the stack-trace massages понеділок, 5 листопада 2018 р. 19:59:15 UTC+1 користувач brad написав: > > Hi, > > Two issues that often frustrate me with GWT deobfuscated stack traces: > a) The stack trace is deobfuscated, but the error message is not, so you > get something like "com.google.gwt.core.client.JavaScriptException: > (TypeError) : Cannot read property 'a' of undefined". > b) The stack trace refers to methods headers, rather than specific lines. > > In many cases, neither of these is a big deal, but if the message is > obscure and the method in question is long it can make debugging difficult. > Is there anything that can be done to work around this (compiler > properties, etc.). This is particularly for debugging a deployed > application, not locally using super dev mode. > > Thanks, > Brad > -- 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: Compilation issue on GWT 2.8.2 (modular maven project)
> On 13 Nov 2018, at 10:58, Thomas Broyer wrote: > > remove scope=provided and classifier=sources from test-shared > remove the jaxb dependency from test-server > possibly add the jaxb dependency with classifier=sources in test-client > Thanks Thomas, it works (with this changes): Added jaxb as dependency in the shared project as: javax.xml.bind jaxb-api 2.3.0 Added jaxb as dependency in the client project as: javax.xml.bind jaxb-api 2.3.0 sources I keep the dependency on the server side, but I will try to remove it with the real project to see if then passes all the tests! Thanks for the help!!! -- Luca Morettoni | http://www.morettoni.net http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni -- 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: Compilation issue on GWT 2.8.2 (modular maven project)
You're doing your dependencies backwards actually. - test-shared does depend on jaxb annotations, but not their sources. Actually, with Java 11, which no longer ships jaxb, it doesn't even compile. - test-server doesn't directly depend on jaxb annotations (AFAICT), and could have the dependency transitively from test-shared. - test-client needs the jaxb annotations as dependency (see https://github.com/gwtproject/gwt/issues/9612, it won't find the jaxb annotations from the JDK), and it actually doesn't even need their sources (but in case you'd need them, this is where you'd put the dependency) So: - remove scope=provided and classifier=sources from test-shared - remove the jaxb dependency from test-server - possibly add the jaxb dependency with classifier=sources in test-client On Monday, November 12, 2018 at 6:51:03 PM UTC+1, Luca Morettoni wrote: > > Hello, I’m using the Thomas Broyer fantastic plugin[1] for maven to split > my project into multiple subproject (client, shared and server). > Until now I used GWT version 2.8.1, but today I started a new project and > I’d like to use the latest version (2.8.2), and some of the POJOs I use in > the shared module will be used also in the server module as a response for > some REST call (with Jersey). > Usually I annotate my POJOs with the usual @XmlRootElement to use it also > in the response payload of a REST call; but switching to 2.8.2 version of > GWT I got the known error: > > [INFO] [ERROR] Errors in > 'file:/Users/luca/tmp/gwt/test/test-shared/src/main/java/net/morettoni/GreetingResponse.java' > [INFO] [ERROR] Line 22: XmlTransient cannot be resolved to a type > [INFO] [ERROR] Line 4: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 8: XmlRootElement cannot be resolved to a type > [INFO] [ERROR] Line 3: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 31: XmlTransient cannot be resolved to a type > > and as I see in the messages in this mailing list the solution is to add > this extra dependency: > > > javax.xml.bind > jaxb-api > ... > sources > provided > > > but I continue to get the same error running the SDM code server (mvn > gwt:codeserver -pl *-client -am), even if I added the above to the pom.xml > of the shared module. > > Any idea on how to fix this issue? I’m using JAVA version 1.8 to compile > and run the attached example. > Thanks in advance for the help! > > [1]: https://github.com/tbroyer/gwt-maven-archetypes > > -- > Luca Morettoni | http://www.morettoni.net > http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni > -- 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: Compilation issue on GWT 2.8.2 (modular maven project)
provided dependencies are not transitive. you need to add the dependency to the client package as well. Am Montag, 12. November 2018 18:51:03 UTC+1 schrieb Luca Morettoni: > > Hello, I’m using the Thomas Broyer fantastic plugin[1] for maven to split > my project into multiple subproject (client, shared and server). > Until now I used GWT version 2.8.1, but today I started a new project and > I’d like to use the latest version (2.8.2), and some of the POJOs I use in > the shared module will be used also in the server module as a response for > some REST call (with Jersey). > Usually I annotate my POJOs with the usual @XmlRootElement to use it also > in the response payload of a REST call; but switching to 2.8.2 version of > GWT I got the known error: > > [INFO] [ERROR] Errors in > 'file:/Users/luca/tmp/gwt/test/test-shared/src/main/java/net/morettoni/GreetingResponse.java' > [INFO] [ERROR] Line 22: XmlTransient cannot be resolved to a type > [INFO] [ERROR] Line 4: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 8: XmlRootElement cannot be resolved to a type > [INFO] [ERROR] Line 3: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 31: XmlTransient cannot be resolved to a type > > and as I see in the messages in this mailing list the solution is to add > this extra dependency: > > > javax.xml.bind > jaxb-api > ... > sources > provided > > > but I continue to get the same error running the SDM code server (mvn > gwt:codeserver -pl *-client -am), even if I added the above to the pom.xml > of the shared module. > > Any idea on how to fix this issue? I’m using JAVA version 1.8 to compile > and run the attached example. > Thanks in advance for the help! > > [1]: https://github.com/tbroyer/gwt-maven-archetypes > > -- > Luca Morettoni | http://www.morettoni.net > http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni > -- 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: Compilation issue on GWT 2.8.2 (modular maven project)
By just adding sources to jaxb it will not work. You need to have these sources in a gwt source folder. so it javax.xml.bind package must be declared as a source folder in a gwt.xml files before the GWT compiler picks it up to cross compile. I don't think that adding the package in you module.gwt.xml will work since there are probably some java files in there that are refering to non supported JRE classes. But you could try with excluding those classes. Regards, David On Monday, November 12, 2018 at 6:51:03 PM UTC+1, Luca Morettoni wrote: > > Hello, I’m using the Thomas Broyer fantastic plugin[1] for maven to split > my project into multiple subproject (client, shared and server). > Until now I used GWT version 2.8.1, but today I started a new project and > I’d like to use the latest version (2.8.2), and some of the POJOs I use in > the shared module will be used also in the server module as a response for > some REST call (with Jersey). > Usually I annotate my POJOs with the usual @XmlRootElement to use it also > in the response payload of a REST call; but switching to 2.8.2 version of > GWT I got the known error: > > [INFO] [ERROR] Errors in > 'file:/Users/luca/tmp/gwt/test/test-shared/src/main/java/net/morettoni/GreetingResponse.java' > [INFO] [ERROR] Line 22: XmlTransient cannot be resolved to a type > [INFO] [ERROR] Line 4: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 8: XmlRootElement cannot be resolved to a type > [INFO] [ERROR] Line 3: The import javax.xml.bind cannot be > resolved > [INFO] [ERROR] Line 31: XmlTransient cannot be resolved to a type > > and as I see in the messages in this mailing list the solution is to add > this extra dependency: > > > javax.xml.bind > jaxb-api > ... > sources > provided > > > but I continue to get the same error running the SDM code server (mvn > gwt:codeserver -pl *-client -am), even if I added the above to the pom.xml > of the shared module. > > Any idea on how to fix this issue? I’m using JAVA version 1.8 to compile > and run the attached example. > Thanks in advance for the help! > > [1]: https://github.com/tbroyer/gwt-maven-archetypes > > -- > Luca Morettoni | http://www.morettoni.net > http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni > -- 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.
