ok. That makes sense
On Tue, Feb 17, 2015 at 11:46 AM, Fabien DUMAY <fabien.dumay@gmail.com> wrote:
Hi Joseph,Thank you for the feedbacks and i'am happy that you like this plugin.It's true that the format of the .gwt.xml files are a little bit verbose and looks easy to generate but in fact it's not.There is many data in those files, module inheritance, generators, property settings...If we imagine integrate those data in the build.gradle, we will lose all benefits of this plugin (clear, simple) adding to that if we change something on that .gwt.xml while the SDM is running, the changes are handled when you reload the page.You can maybe submit an alternative format to the GWT contributors in order to see what do they think about it.For my part we will soon provide a task for initializing that file, but it will be almost emptyI still available for any question.Regards,It's true that the format of the .gwt.xml are a little bit verboseLe 17 févr. 2015 à 17:09, Joseph Gardi <jgleoj23@gmail.com> a écrit :To post to this group, send email to google-web-toolkit@googlegroups.com.I just finished converting my maven app to gradle with this plugin and it really is faster and easier. The build.gradle file is 5 times shorter than my old pom and clearer. Gradle is significantly faster to. I like it so much that it'd be nice if I could replace my gwt.xml files with gradle too. I don't want to just embed the same xml in the build.gradle though. I'd want this feature to have same syntax awesomeness as gradle. If the plugin handles the gwt.xml files it can have more control and achieve tighter integration. Also, this feature would reduce boilerplate code. Currently, I have to add dependencies in my build.gradle and then inherit the modules in my gwt.xml file. I'd be embarassed to say how many times I forgot to inherit the modules. With this feature I could just add the dependency once in my build.gradle file. I think this would be fairly simple to implement and I'm willing to do it later but I don't want to do it until I become more familiar with gradle.
On Tuesday, February 17, 2015 at 10:08:03 AM UTC-5, confile wrote:Done.!
Am Dienstag, 17. Februar 2015 15:36:07 UTC+1 schrieb Fabien Dumay:I agree the need, can you please raise an issue on GitHub, I'll do it within the week (i guess tomorrow).Le 17 févr. 2015 à 15:29, confile <michael....@googlemail.com> a écrit :Well, I need a gwtSuperDev mode task. It would be great if you could add this to your plugin. The code server should run independently of an application server. This gives you more freedom of choice.
Am Dienstag, 17. Februar 2015 15:24:08 UTC+1 schrieb Fabien Dumay:Yes it should fix it.I had the problem with the GWT Gradle plugin that when I run in gradle gwtSuperDev and included a second project in my main project that only the sources of my main projects are recompiled using SuperDevMode. When I get you correct you solved this problem. Is this correct?The gwtDev task runs the SDM + Jetty with the same ease as the DevMode (no bookmarklet is require).Also is your gwtDev task running only the SuperDevMode? If not is there a way to run it standalone in your plugin?The gwtSuperDev task doesn't exist yet. If you need it, it would be pretty simple to implement. The weak point to that task would be the requirement of the bookmarklet.Michael
Am Dienstag, 17. Februar 2015 14:33:46 UTC+1 schrieb Fabien Dumay:Hi Confile,
I worked for a while with the gwt-gradle-plugin and it works pretty fine.
Actually, there were two main points that was annoyed me:
1 - the gwtDev task runs the standard gwt DevMode. It limiting me by runnig the server side on a Jetty 8 which doesn't support the websocket (JSR 358).
2 - The sources from the other projects (multimodule with libs) are not automatically added to the SDM, so we need to relaunch the gradle gwtSuperDev task to view the changes.So to solve it, the gwtDev task runs two external java processes; the first one starts the CodeServer including all sources from all project dependencies i.e. comile project(":my-lib"), and the other one starts the webapp on Jetty 9 without extra library in the classpath such as gwt-dev.jar.
After those two points, I'd love to implement some extra tasks :
- gwtSetup to initialize the project from templates like maven is doing with archetypes
- extra app containers (Tomcat, WildFly...)
- some packaging tasks to build some native app (webviews) on iOS and AndroidWith many perspectives in order to make developpers life simpler.
I hope to light you on the why and what is this plugin.
I still available for any question.
Regards,
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://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 "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://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 "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
Visit this group at http://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 a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/EVZQ-Cvrqq0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://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 "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment