[gwt-contrib] GPE does not like GWT trunk SDK?
We are start using GWT trunk builds for development but Eclipse / GPE always says GWT SDK ... on the projects build path is not valid (Version is not supported, must be 2.0.0 or later) if we add a trunk build to the list of GWT SDKs in Eclipse. In the list of GWT SDKs the version column is empty so it seems like Eclipse does not recognize any version. This happens for a typically GWT SDK 0.0.0 build and it also happens if I set the env.GWT_VERSION property to anything above 2.0.0. Is there anything I forgot to configure prior calling the ant script to make Eclipse happy? -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GPE does not like GWT trunk SDK?
Looks like commit https://gwt.googlesource.com/gwt/+/db1b5bc561c3a4826002447b88401d626dc750bf breaks the current Google Eclipse Plugin's SDK version detection as it probably checks against the removed GWT_VERSION field. So GWT 2.6 probably also needs a GPE update. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GPE does not like GWT trunk SDK?
Luckily the mechanism of Googles Eclipse Plugin to detect GWT Maven dependencies does not do the version check. So as a workaround I can remove the GWT facet, add GWT libraries manually and re-add the GWT facet on the project. The plugin then accepts the manually added GWT libraries as GWT SDK. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GPE does not like GWT trunk SDK?
And as a nit pick: While searching for the reason for the problem I noticed that @GWT_SVNREV@ has been changed to @GWT_GITREV@ in https://gwt.googlesource.com/gwt/+/05c7aeb80335bb834659176989d0d984b01da2c8 But the files distro-source/core/src/ about.html about.txt have not been updated to @GWT_GITREV@. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GPE does not like GWT trunk SDK?
Luckily the mechanism of Googles Eclipse Plugin to detect GWT Maven dependencies does not do the version check. So as a workaround I can remove the GWT facet, add GWT libraries manually and re-add the GWT facet on the project. The plugin then accepts the manually added GWT libraries as GWT SDK. Have to correct myself because Eclipse tricked me because a project dependency had GWT 2.5.1 configured, so 2.5.1 was on class path. Configured both projects with GWT trunk and Eclipse is unhappy again. Looks like I have to revert the mentioned commit locally for now. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] Re: GPE does not like GWT trunk SDK?
For reference: https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=246 -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: Maven-ization Status
* dependencies have to be deployed to a Maven repo I wanted to chime in here, the dependencies to build a splattered hierarchy of java with poms using intellij to back-fill dependencies is here, tested on 2.5.0--rc i beleive. repository idgwt-maven-rewraps/id urlhttp://gwt-maven-rewraps.googlecode.com/git//url /repository if intellij can backfill gradle builds the same way it backfills with maven deps, all the better. in my experience things reach a point of mvn clean install with poms if you cordone off unit test support to be last and then don't run the unit tests. On Wednesday, October 2, 2013 9:29:46 AM UTC-7, Thomas Broyer wrote: On Wednesday, October 2, 2013 4:48:14 PM UTC+2, Geoffrey Wiseman wrote: On Sunday, September 29, 2013 8:51:47 PM UTC-4, Matthew Dempsky wrote: Anyway, I'm of the same opinion here as Thomas: I want to make it easy for developers to use GWT in their projects and to contribute to GWT itself. I supported switching to Maven as a means to this end, but I'm no fan of it beyond that, and I don't think any other core GWT contributors are at this point. To summarize: if anyone still feels strongly that GWT should use Maven, those individuals need to roll up their sleeves and work on making it happen. I neither love or hate Maven. It's one of the best supported build tools in Java, and I end up using it for that reason as much as anything else. It simplifies some things and makes other things more complex. If one of its alternatives got really popular, I would probably try it. In the end, I probably prefer Maven to Ant, mainly because Maven projects /tend/ to be a little more likely to work out of the box without configuration on an individual developer's machine, but that's more to do with how people use Ant than with Ant itself. That said, I agree with a bunch of the comments here that getting GWT to the point where someone can contribute to it without days of setup is key; I once tried to contribute a patch to something, but after a few hours of not getting the project fully set up, I gave up and went back to what I was actually working on. If you can reduce the barrier to entry so that it's not hard to contribute, even if that means installing Gradle or Buck, I think the problem is solved. If you moved to Maven and still had immense setup hurdles, the problem still isn't solved, AFAICS. The main issue with Maven here is that the road is long to reach a state where setting up your dev env is a breeze: * dependencies have to be deployed to a Maven repo * code *has* to be modularized a bit (because, as I said, gwt-dev tests depend on gwt-user and the hello sample sources) There might be some intermediary steps but we'd then lose features of the build (e.g. no gwt-dev tests), and/or it wouldn't solve the setup issue (if you don't deploy deps to a Maven repo) So moving to Maven requires a big bang move, i.e. the easiest way to fail. Gradle allows for baby steps: 1) make it work 2) make it better 3) modularize, piece by piece. Buck would require some work to setup IDEs, including hand-generating Eclipse .project/.classpath files by hand. So, I'd just be happy if that barrier to entry could be reduced -- reduced setup, increased modularity, simpler out-of-the-box configuration, etc. That'd make it easier for people like me to be more involved. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?
have not been updated to @GWT_GITREV@. Thanks! Good catch. https://gwt-review.googlesource.com/#/c/5194/ - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?
I was going to ask how active the GPE project is...is the last commit really from October 2012? https://code.google.com/p/google-plugin-for-eclipse/source/list That doesn't seem right, but AFAICT there isn't another source repo? https://developers.google.com/eclipse/community - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
[gwt-contrib] String concatenation
Dear GWT lovers, I have a question for the compiler guys : in the CssResource I see a comment mentioning that very large string concatenation expressions using '+' cause the GWT compiler to overflow the stack due to deep AST nesting. So it's preferable to use intermediate concatenation groupings in order to force the AST to be more balanced. I'm just wondering if this issue is still present with the actual version of the compiler or if it was fixed to better handle large concatenation ? Thanks, Julien -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] String concatenation
oh you mean in CssResourceGenerator.java found it, taking a look On Wed, Oct 30, 2013 at 1:22 PM, John Stalcup stal...@google.com wrote: can you link me to that comment? i'm unfamiliar. On Wed, Oct 30, 2013 at 1:10 PM, Julien Dramaix julien.dram...@gmail.comwrote: Dear GWT lovers, I have a question for the compiler guys : in the CssResource I see a comment mentioning that very large string concatenation expressions using '+' cause the GWT compiler to overflow the stack due to deep AST nesting. So it's preferable to use intermediate concatenation groupings in order to force the AST to be more balanced. I'm just wondering if this issue is still present with the actual version of the compiler or if it was fixed to better handle large concatenation ? Thanks, Julien -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] String concatenation
can you link me to that comment? i'm unfamiliar. On Wed, Oct 30, 2013 at 1:10 PM, Julien Dramaix julien.dram...@gmail.comwrote: Dear GWT lovers, I have a question for the compiler guys : in the CssResource I see a comment mentioning that very large string concatenation expressions using '+' cause the GWT compiler to overflow the stack due to deep AST nesting. So it's preferable to use intermediate concatenation groupings in order to force the AST to be more balanced. I'm just wondering if this issue is still present with the actual version of the compiler or if it was fixed to better handle large concatenation ? Thanks, Julien -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] String concatenation
Not a compiler expert, but I wouldn't be surprised since in the AST it will be represented as a binary tree of JBinaryOperation nodes and the visitors walk the tree recursively. So balancing the tree should result in a smaller stack. - Brian On Wed, Oct 30, 2013 at 1:10 PM, Julien Dramaix julien.dram...@gmail.comwrote: Dear GWT lovers, I have a question for the compiler guys : in the CssResource I see a comment mentioning that very large string concatenation expressions using '+' cause the GWT compiler to overflow the stack due to deep AST nesting. So it's preferable to use intermediate concatenation groupings in order to force the AST to be more balanced. I'm just wondering if this issue is still present with the actual version of the compiler or if it was fixed to better handle large concatenation ? Thanks, Julien -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [gwt-contrib] String concatenation
On Wed, Oct 30, 2013 at 4:26 PM, Brian Slesinsky skybr...@google.comwrote: Not a compiler expert, but I wouldn't be surprised since in the AST it will be represented as a binary tree of JBinaryOperation nodes and the visitors walk the tree recursively. So balancing the tree should result in a smaller stack. Right, the issue is that a long run of concatenation resulted in a degenerate tree like concat(a,concat(b,concat(c,...))) and you could blow out the stack on a recursive traversal. I remember discussions about special-casing string concatenation (it seemed unlikely to affect other operators), either into a balanced tree or simply a multi-arg concat operator. I don't know if anything was ever done. -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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. For more options, visit https://groups.google.com/groups/opt_out.
