Re: [gwt-contrib] Re: Question to Windows users
Sounds like a hasle to require a VM... unless that VM would include everything to get started. Just setting up eclipse to be inline with the coding guidelines in GWT and setting up all the libraries etc are really painful and you need to follow the steps very carefully (and hopefully no dependency has been changed since the document was written). What we do (in an enterprise environment) is to just have a zip or machine image ready to be installed on a new machine. After 30 minutes or so a new developer is ready to code. On Sat, Oct 18, 2014 at 7:25 PM, Brandon Donnelson branflake2...@gmail.com wrote: Setting up an images seems ideal to me to get going with less steps. On Friday, October 17, 2014 3:04:05 PM UTC-7, Thomas Broyer wrote: On Friday, October 17, 2014 5:11:10 PM UTC+2, Rene Hangstrup Møller wrote: I am just going to repeat my reply from google+ here: If you want to encourage contributions from the community, you should work on lowering the barriers to entry. Pick standard tools that work on a variety of platforms. What went wrong with the conversion to gradle? Nothing went wrong, but handling external dependencies still requires that you svn co and svn up the gwt-tools repo, and Gradle will most likely impact how we'd later modularize GWT (not necessarily a bad thing, but something to be aware of). I'll make a comparison matrix of Gradle vs. Buck vs. Pants when I find time. Why do you need some obscure build system where first sentence on the install page is As of September 2014, alas, Pants is not something you can just install and use. It also says that “Once it’s set up, most folks should be able to use the Pants Conceptual Overview https://pantsbuild.github.io/first_concepts.html and not worry about these things.”, i.e. “pants goal idea” or “pants goal eclipse” to setup your IDE, “pants goal jar” and “pants goal test” for everyday use, “pants goal publish” or “pants goal bundle” to build GWT in order to use it in your projects (deploy it in a Maven repo, or create a ZIP with all needed JARs) Note: I haven't tried Pants yet, so this is all from the docs. Existing repositories seem to have a bunch of scripts in them so you can just “git clone” and run “./pants” and Pants will download itself, just like Gradle with ./gradlew. And BUILD files are easy to read and self-explanatory. -- 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/5f8f2899-82a2-4b06-aca3-9f2554546d3c%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/5f8f2899-82a2-4b06-aca3-9f2554546d3c%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 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/CABrJHW3eNQEA5Ne9JY4w4AbvqDUvXWS%3D%2B0L-8k%3D%3DxuThaXPxXA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7.0 beta1
I'm seeing what looks like a regression in my project. I get the following error when running GWT compilation from Gradle after upping the version. The error doesn't seem very helpful except that it's possibly related to code generation and UiBinder: Compiling module com.MyModule Computing all possible rebind results for 'com.mypackage.MyView.MyUiBinder' Rebinding com.mypackage.MyView.MyUiBinder Checking rule replace-with class='com.mypackage.environment.TestEnvironment'/ [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly [ERROR] Errors in 'com/mypackage/MyViewView.java' [ERROR] Line 36: Failed to resolve 'com.mypackage.MyView.MyUiBinder' via deferred binding [...many similar errors for other UiBinders...] On Saturday, October 18, 2014 10:54:40 AM UTC-7, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- 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/70fec55a-2563-4729-8397-29a326e5e9bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Change packaging for GSS
https://gwt-review.googlesource.com/9810 On Sun, Oct 19, 2014 at 12:47 AM, Julien Dramaix julien.dram...@gmail.com wrote: I will work on that tomorrow On Oct 18, 2014 8:10 PM, 'Daniel Kurka' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Hi all, apparently we ended up packaging gss into gwt-dev instead of gwt-user: https://gwt-review.googlesource.com/#/c/9803/ @Thomas, @Julien can you guys look into providing a patch that moves this into gwt-user? -Daniel -- 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/CALLujipLY9ydhxTG0__D0vVojSpuCGQAmLb1aD-rPOBz1Me62A%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipLY9ydhxTG0__D0vVojSpuCGQAmLb1aD-rPOBz1Me62A%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/CABb_3%3D4v%3Dt8WUAamukrbz%3DGU9YhXyfE7d0UK8RBg-txR2aykCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
Does adding inherit to c.g.gwt.uibinder.UiBinder fix the issue? We broke many cyclic dependencies around c.g.gwt.user.User. In this process, I dropped many unneeded dependencies to User from smaller modules. As most developers directly depend on User that doesn't have any affect. However if they were depending another module (e.g. Validation) and getting User dependency transitively from there, they will break. I didn't close analyzed but some potential packages that no longer depend on User are: com/google/gwt/validation/Validation.gwt.xml com/google/gwt/xml/XML.gwt.xml com/google/web/bindery/autobean/AutoBean.gwt.xml com/google/gwt/storage/Storage.gwt.xml com/google/gwt/i18n/... com/google/gwt/event/dom/... On Sun, Oct 19, 2014 at 12:51 PM, Erik Kuefler ekuef...@gmail.com wrote: I'm seeing what looks like a regression in my project. I get the following error when running GWT compilation from Gradle after upping the version. The error doesn't seem very helpful except that it's possibly related to code generation and UiBinder: Compiling module com.MyModule Computing all possible rebind results for 'com.mypackage.MyView.MyUiBinder' Rebinding com.mypackage.MyView.MyUiBinder Checking rule replace-with class='com.mypackage.environment.TestEnvironment'/ [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly [ERROR] Errors in 'com/mypackage/MyViewView.java' [ERROR] Line 36: Failed to resolve 'com.mypackage.MyView.MyUiBinder' via deferred binding [...many similar errors for other UiBinders...] On Saturday, October 18, 2014 10:54:40 AM UTC-7, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- 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/70fec55a-2563-4729-8397-29a326e5e9bf%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/70fec55a-2563-4729-8397-29a326e5e9bf%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 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%3DyUA3V5--75knM5eEmOcyc%2B-2Esrbdxxbrxkv%3DRmtozgd9LQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
Doesn't seem to help. I did already have a dependency on User. Here's the full list of inherits from my gwtxml: inherits name='com.google.gwt.user.User'/ inherits name='com.google.gwt.uibinder.UiBinder'/ inherits name=com.google.gwt.logging.Logging/ inherits name='com.google.gwt.user.theme.clean.Clean'/ inherits name=com.google.common.collect.Collect/ inherits name=com.google.gwt.inject.Inject/ inherits name=com.google.common.base.Base/ inherits name=com.google.gwt.ajaxloader.AjaxLoader / inherits name=com.google.web.bindery.autobean.AutoBean/ inherits name='gwt.g3d.g3d'/ !-- some internal modules -- inherits name=elemental.Elemental / On Sun, Oct 19, 2014 at 3:03 PM, 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Does adding inherit to c.g.gwt.uibinder.UiBinder fix the issue? We broke many cyclic dependencies around c.g.gwt.user.User. In this process, I dropped many unneeded dependencies to User from smaller modules. As most developers directly depend on User that doesn't have any affect. However if they were depending another module (e.g. Validation) and getting User dependency transitively from there, they will break. I didn't close analyzed but some potential packages that no longer depend on User are: com/google/gwt/validation/Validation.gwt.xml com/google/gwt/xml/XML.gwt.xml com/google/web/bindery/autobean/AutoBean.gwt.xml com/google/gwt/storage/Storage.gwt.xml com/google/gwt/i18n/... com/google/gwt/event/dom/... On Sun, Oct 19, 2014 at 12:51 PM, Erik Kuefler ekuef...@gmail.com wrote: I'm seeing what looks like a regression in my project. I get the following error when running GWT compilation from Gradle after upping the version. The error doesn't seem very helpful except that it's possibly related to code generation and UiBinder: Compiling module com.MyModule Computing all possible rebind results for 'com.mypackage.MyView.MyUiBinder' Rebinding com.mypackage.MyView.MyUiBinder Checking rule replace-with class='com.mypackage.environment.TestEnvironment'/ [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly [ERROR] Errors in 'com/mypackage/MyViewView.java' [ERROR] Line 36: Failed to resolve 'com.mypackage.MyView.MyUiBinder' via deferred binding [...many similar errors for other UiBinders...] On Saturday, October 18, 2014 10:54:40 AM UTC-7, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- 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/70fec55a-2563-4729-8397-29a326e5e9bf%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/70fec55a-2563-4729-8397-29a326e5e9bf%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/vCELYDM2_tE/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
Re: [gwt-contrib] Re: GWT 2.7.0 beta1
I don't have any other ideas. If you can provide us a simpler repro case, it would be very helpful. On Sun, Oct 19, 2014 at 3:11 PM, Erik Kuefler ekuef...@gmail.com wrote: Doesn't seem to help. I did already have a dependency on User. Here's the full list of inherits from my gwtxml: inherits name='com.google.gwt.user.User'/ inherits name='com.google.gwt.uibinder.UiBinder'/ inherits name=com.google.gwt.logging.Logging/ inherits name='com.google.gwt.user.theme.clean.Clean'/ inherits name=com.google.common.collect.Collect/ inherits name=com.google.gwt.inject.Inject/ inherits name=com.google.common.base.Base/ inherits name=com.google.gwt.ajaxloader.AjaxLoader / inherits name=com.google.web.bindery.autobean.AutoBean/ inherits name='gwt.g3d.g3d'/ !-- some internal modules -- inherits name=elemental.Elemental / On Sun, Oct 19, 2014 at 3:03 PM, 'Goktug Gokdogan' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: Does adding inherit to c.g.gwt.uibinder.UiBinder fix the issue? We broke many cyclic dependencies around c.g.gwt.user.User. In this process, I dropped many unneeded dependencies to User from smaller modules. As most developers directly depend on User that doesn't have any affect. However if they were depending another module (e.g. Validation) and getting User dependency transitively from there, they will break. I didn't close analyzed but some potential packages that no longer depend on User are: com/google/gwt/validation/Validation.gwt.xml com/google/gwt/xml/XML.gwt.xml com/google/web/bindery/autobean/AutoBean.gwt.xml com/google/gwt/storage/Storage.gwt.xml com/google/gwt/i18n/... com/google/gwt/event/dom/... On Sun, Oct 19, 2014 at 12:51 PM, Erik Kuefler ekuef...@gmail.com wrote: I'm seeing what looks like a regression in my project. I get the following error when running GWT compilation from Gradle after upping the version. The error doesn't seem very helpful except that it's possibly related to code generation and UiBinder: Compiling module com.MyModule Computing all possible rebind results for 'com.mypackage.MyView.MyUiBinder' Rebinding com.mypackage.MyView.MyUiBinder Checking rule replace-with class='com.mypackage.environment.TestEnvironment'/ [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly [ERROR] Errors in 'com/mypackage/MyViewView.java' [ERROR] Line 36: Failed to resolve 'com.mypackage.MyView.MyUiBinder' via deferred binding [...many similar errors for other UiBinders...] On Saturday, October 18, 2014 10:54:40 AM UTC-7, Daniel Kurka wrote: Hi all, since we are adding major features to GWT, we decided to change our release process for GWT 2.7. I just published GWT 2.7.0-beta1 to maven central and our file storage http://goo.gl/pr7km3. We are doing this beta to get external feedback on incremental compilation and GSS. Incremental compilation is now default with GWT 2.7 and replaces, together with Super dev mode, the regular old dev mode. Inside of Google we are already using it for a while now and most of the issues should have already been dealt with, however we also want to make sure that external users that might have slightly different use cases will have a working 2.7.0 release. So please start testing with beta1 and give us lots of feedback on the contributor list https://groups.google.com/forum/#!forum/Google-Web-Toolkit-Contributors or on the issue tracker https://code.google.com/p/google-web-toolkit/issues/list. Please keep in mind that we did not do any release testing on beta1, so there might be issues that you do not expect from a release candidate. Our current plan is to wait until the end of next week for any feedback. If we do not find any serious external issues we will start the testing process for an actual release candidate. -Daniel -- 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/70fec55a-2563-4729-8397-29a326e5e9bf%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/70fec55a-2563-4729-8397-29a326e5e9bf%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/vCELYDM2_tE/unsubscribe . To unsubscribe from this group and all its topics, send an email to
[gwt-contrib] odd super dev mode times
Hi, I'm trying out GWT 2.7.0-beta1, and am seeing kind of odd recompile times. (Our app is ~70k LOC, and the main/only generators are GWT-RPC and UiBinder.) The first compile take 40s. Then, only changing a single char in a .java file, the first recompile takes 20s. Then each next one takes consistently ~10-15s. However, eventually something magical happens, and we hit 3s. The 3s is great. The first 40s is known/understandable. But I can't figure out what's happening with these ~10-20s recompiles in the middle. ...and, right now, I can't even get the 3s time to kick in again. Here is the compile output from two attempts: https://gist.github.com/stephenh/9eecf293570b8d5c5eee I assume the idea it should immediately go from 40s to 3s? Any ideas about how to debug the faster but not quite fast compiles? (I suppose an obvious one is to kick up the log level; I should have tried that already, and will later.) Thanks, Stephen -- 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/20141019191825.4c11fd77%40sh9. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: odd super dev mode times
...and, right now, I can't even get the 3s time to kick in again. Ah ha...seems to be something with the PersistentUnitCache. When the recompile is 10-20s every time, I see output of: Wrote 4944 units to persistent cache Wrote 1 units to persistent cache (reload) Wrote 4944 units to persistent cache Wrote 1 units to persistent cache (reload) Wrote 4944 units to persistent cache Wrote 1 units to persistent cache I nuked my gwt-unitCache dir, and then see: (on startup) Wrote 4944 units to persistent cache (first load) Wrote 1 units to persisent cache ...this (Wrote 1 unit) repeated 100s of times... Purging cache files Wrote 6166 units to persistent cache Wrote 4945 units to persistent cache Wrote 1 units to persistent cache ...few more 1 units... (reload) Wrote 1 units to persistent cache (reload) Wrote 1 units to persistent cache I'm now getting the 3s reload. I restarted devmode 2-3x and it still worked great. However, on the 4th-5th restart, the old behavior came back. Nuking my gwt-unitCache re-fixed it. - Stephen -- 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/20141019211649.6a1a0307%40sh9. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: odd super dev mode times
John detected that behavior in the persistent unit cache and has a fix for it. On Oct 19, 2014 7:16 PM, Stephen Haberman stephen.haber...@gmail.com wrote: ...and, right now, I can't even get the 3s time to kick in again. Ah ha...seems to be something with the PersistentUnitCache. When the recompile is 10-20s every time, I see output of: Wrote 4944 units to persistent cache Wrote 1 units to persistent cache (reload) Wrote 4944 units to persistent cache Wrote 1 units to persistent cache (reload) Wrote 4944 units to persistent cache Wrote 1 units to persistent cache I nuked my gwt-unitCache dir, and then see: (on startup) Wrote 4944 units to persistent cache (first load) Wrote 1 units to persisent cache ...this (Wrote 1 unit) repeated 100s of times... Purging cache files Wrote 6166 units to persistent cache Wrote 4945 units to persistent cache Wrote 1 units to persistent cache ...few more 1 units... (reload) Wrote 1 units to persistent cache (reload) Wrote 1 units to persistent cache I'm now getting the 3s reload. I restarted devmode 2-3x and it still worked great. However, on the 4th-5th restart, the old behavior came back. Nuking my gwt-unitCache re-fixed it. - Stephen -- 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/20141019211649.6a1a0307%40sh9 . 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/CAC7T7gk_0zZ2e5huLO9fKGE_uKBdoGDKQUqMjcm95fZgPjBChw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] odd super dev mode times
The time it takes to compile depends not only on how many files are modified but also how big is the invalidation caused by the modification. Depending what gets invalidated it might require running more generators or (re) compiling many more types. Also the first few compiles are also warming up the JVM, jit and all. -- 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/CAC7T7gnvMK1m8ET4TKtjWfdodrxEnE8P4cocehW2ozD2uhKpQg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: odd super dev mode times
depends on how many files are modified [+ invalidations] Yeah, sorry, I should have mentioned I've only been changing one file, just adding/removing a character in a string. John detected that behavior in the persistent unit cache and has a fix for it. Great! I'll try it out when it hits master. - Stephen -- 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/20141019215142.6e6e53f1%40sh9. For more options, visit https://groups.google.com/d/optout.
