Re: [gwt-contrib] I think the 2.7.0 GWT release was compiled on Daniel Kurka's machine !
It's not my desktop machine, but you are right I did the final compilation of the release. I thought we had already killed of gwttars anyway. On Thu, Jul 2, 2015, 11:21 AM Arnaud TOURNIER ltea...@gmail.com wrote: Hi Daniel, I had a closer look to the thing. The paths mentionning your home account in google are stored in all the gwtar files in the gwt-user-2.7.0 artifact Does that really mean that the offical gwt releases are built on your desktop machine ? Thanks Arnaud Le mer. 1 juil. 2015 à 18:42, Arnaud TOURNIER ltea...@gmail.com a écrit : It's a project of one of my customers which is on gwt 2.6 and needs to migrate to 2.7. In the cours of doing that, i got this errors... If you need, i can investigate a bit more, but seems to be coming from those [ERROR] java.lang.String cannot be resolved to a class... Thanks ARnaud Le mer. 1 juil. 2015 à 18:20, 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com a écrit : Hi Arnaud, how are you producing these? -Daniel On Wed, Jul 1, 2015 at 9:06 AM Arnaud TOURNIER ltea...@gmail.com wrote: Just dumping a bit of errors i get for a project : Tracing compile failure path for type 'java.lang.Object' [INFO] [ERROR] Errors in 'file: */usr/local/google/home/dankurka/gwt/user/super/co* m/google/gwt/emul/java/lang/Object.java' [INFO] [ERROR] java.lang.String cannot be resolved to a type [INFO] [ERROR] Errors in 'file:/usr/local/google/home/*dankurka* /gwt/user/src/com/google/gwt/core/client/JavaScriptObject.java' [INFO] [ERROR] java.lang.String cannot be resolved to a type [INFO] [ERROR] Errors in 'file:/usr/local/google/home/*dankurka* /gwt/user/super/com/google/gwt/emul/java/lang/Throwable.java' [INFO] [ERROR] java.lang.String cannot be resolved to a type [INFO] [ERROR] Errors in 'file:/usr/local/google/home/*dankurka* /gwt/user/super/com/google/gwt/emul/java/lang/Class.java' There's no bug, nor problem on GWT side. I just found funny to get those kind of paths in a release artifact !! Thanks Arnaud -- 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/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/4a744841-48ca-4a75-a5e4-91ba966aea80%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups GWT Contributors group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit-contributors/SyRZzSQeDWg/unsubscribe . To unsubscribe from this group and all its topics, 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/CALLujiqP2rwYW9e2eqDUxL8qUA-5VKaGFbGi4bPS_-sNbGN3HA%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqP2rwYW9e2eqDUxL8qUA-5VKaGFbGi4bPS_-sNbGN3HA%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDncCZn1u3Pg%3DH%2B7AqZ0p%3Dcw5KADTmZx%2B3E2qeDEyttoCkQ%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDncCZn1u3Pg%3DH%2B7AqZ0p%3Dcw5KADTmZx%2B3E2qeDEyttoCkQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipFQmcmy0e_8QpR07r0BtTYnQ8aeX9Xu9RXiSGMsPLd4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Stop calling it GWT 3.0
Sounds like I'm late to party; I missed the 2015 meetup videos, does someone have a link? (That will teach me to not login to G+ very often...well played, Google...) Not that my opinion matters very much (vs. the GWT team who's doing all the actual work), but I'll +100 any plans for large/breaking changes/rewrite for GWT 3.0/j2cl. Everyone that is concerned about backwards compatibility, you can stay on GWT 2.x. What we need is foundations for a GWT that will be awesome 5 years from now. For the next generation of applications. That's who we need to be worried about. Yes, that means pain/being left out for the current generation of applications, but that's how technology works. GWT 2.x will not suddenly be taken off Maven central. Plenty of enterprise applications rely on older/mature technology, e.g. jars/projects that aren't pushing out new releases every 2 months with amazing new features. That's fine. If it's too expensive to switch, then don't. Sounds like a great opportunity for other companies to step-in and provide enterprise support for 2.x as well. Google has never been interested in that game anyway. Someone mentioned early access to j2cl for framework authors to start porting; I'd throw my hat into that ring. It would be interesting to see what Tessell looks like with it. Tessell very heavily uses UiBinder to drive its MVP codegen, so I'll have to either port Tessell to the next-generation of templates, or (more likely) port UiBinder to j2cl (using APT/something; maybe not 100% backwards compatible, but at least something that is not throw away all your templates and start from scratch). - Stephen On Saturday, June 13, 2015 at 4:03:08 AM UTC-5, Paul Robinson wrote: The GWT Meetup 2015 videos are very interesting. I can see why the proposals for GWT 3.0 have been made. However, we should be clear about the fact that GWT 3.0 is not just going to break a few little things that can easily be fixed, but break things to the point that it's a completely different product and there will be lots of GWT applications that will never be ported to the new system. It will be confusing to all GWT users to continue to use the name GWT 3.0. It would be much better to use a new name for the new system and treat it as what it is: a new idea about how Java can be used to build modern web applications. The situation we have now is that GWT will end at 2.8 and a new thing, that is currently vapourware, will be coming that people are expected to use. There's going to be a lot of confusion and those using GWT now, as well as those that will use the new thing when it does exist, will all be served much better if everybody stops calling the new thing GWT. Paul -- 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/afebe594-679a-4ff6-b270-3cb0861986fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Stop calling it GWT 3.0
On Monday, July 6, 2015 at 2:42:04 PM UTC+2, Stephen Haberman wrote: Sounds like I'm late to party; I missed the 2015 meetup videos, does someone have a link? (That will teach me to not login to G+ very often...well played, Google...) https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE (link to the slides is in the playlist description) Not that my opinion matters very much (vs. the GWT team who's doing all the actual work), but I'll +100 any plans for large/breaking changes/rewrite for GWT 3.0/j2cl. Everyone that is concerned about backwards compatibility, you can stay on GWT 2.x. What we need is foundations for a GWT that will be awesome 5 years from now. For the next generation of applications. That's who we need to be worried about. Yes, that means pain/being left out for the current generation of applications, but that's how technology works. GWT 2.x will not suddenly be taken off Maven central. Plenty of enterprise applications rely on older/mature technology, e.g. jars/projects that aren't pushing out new releases every 2 months with amazing new features. That's fine. If it's too expensive to switch, then don't. …with the caveat that “The web is not a platform. It's a continuum.” https://adactio.com/journal/6692, which in terms of browser bugs and browser sniffing means that libraries/frameworks have to be maintained if you expect them to continue to work with newer/future browsers and/or browser versions (remember the mess with every new IE version, requiring changes in GWT? has anyone tried GWT in MS Edge?) Hopefully this is going to stabilize with evergreen browsers, but there's still a limit in time before GWT 2.x explodes and everyone has no choice but migrating to something else (a newer version of GWT, or something else entirely). So saying GWT 2.x is here to stay really would depend on someone maintaining it: Sounds like a great opportunity for other companies to step-in and provide enterprise support for 2.x as well. Google has never been interested in that game anyway. Someone mentioned early access to j2cl for framework authors to start porting; I'd throw my hat into that ring. It would be interesting to see what Tessell looks like with it. As I said elsewhere, you don't have to wait for an early access to j2cl to start porting. Proof (admittedly a simple/limited one): https://github.com/tbroyer/gwt-places Tessell very heavily uses UiBinder to drive its MVP codegen, so I'll have to either port Tessell to the next-generation of templates, or (more likely) port UiBinder to j2cl (using APT/something; maybe not 100% backwards compatible, but at least something that is not throw away all your templates and start from scratch). Re. UiBinder, maybe it could have a first generator pass creating Java source for the *.ui.xml, that could later be reused by an annotation processor working from the owner Java class: what's specific to the *.ui.xml is generated by a first pass (before JavaC) –just like you do with Protocol Buffer and the like–, and the annotation processor (during JavaC) does only what's specific to the owner class (@UiField, @UiHandler, @UiFactory), calling into the previously-generated class for the *.ui.xml-specific things (that class could possibly be subclassed to override methods when the owner class has @UiField(provided=true) or @UiFactory vs. a simple @UiField, for instance) That unfortunately would call for a complete rewrite, and UiBinder is quite complex… But if the alternative is to write something else from scratch, then reusing the *.ui.xml and @UiField contract probably wouldn't be a bad starting point (and ease porting existsing code). But I think we should just stop speculating, wait a bit for Google to continue their experiment with j2cl and have a clearer view of how they want to migrate their existing apps, and then see which features Google would like to port themselves (because they need them anyway) and which ones they'd abandon, and whether they'll be replaced or not. -- 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/50244c3d-81b9-4a57-8fdb-2fc92ce2534c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
