[gwt-contrib] Re: Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
Also just hit the same issue in 2.7.0 Using the -noincremental SDM option seems to get around it, I'd presume though at the expense of recompile speed. On Tuesday, 25 November 2014 16:25:04 UTC+2, Alexander Tarasov wrote: As I can see in gwt 2.7.0 release it was not fixed. collapse-all-properties doesn't help :( -- 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/e9e0810f-1868-4212-88f6-b1c1d907bbaa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
Hello John, could you please clarify if the issue was fixed or not? I have have the same error in 2.7. Is it related to gxt or not? среда, 1 октября 2014 г., 23:08:31 UTC+2 пользователь John Stalcup написал: We have a short list of issues that have to be addressed before 2.7 RC, and this is on the list. On Wed, Oct 1, 2014 at 1:13 AM, Julien Dramaix julien@gmail.com javascript: wrote: I confirm, I just add GXT to one of my test project and I'm not able to use sdm anymore: [ERROR] Current binding properties are expanding to more than one permutation but per-file compilation requires that each compile operate on only one permutation. On Wed, Oct 1, 2014 at 2:34 AM, Colin Alworth nilo...@gmail.com javascript: wrote: The 'test runner' in this case is just the name of a regular module file, which happens to be used for running lots of tests, most of which look like EntryPoints. Nothing too magic going on here, and I've gotten this error by running modules for more 'normal' gwt apps as well, typically when I stop SDM, restart it, and then refresh the browser or click Compile without first using the SDM off bookmarklet. I'm not completely aware of your configuration but... it appears that you're using incremental compiles from a test runner, and this test runner isn't restricting the permutations to just 1. And that is being caught by an assertion. You can fix this by adding some set-property tags to your test .gwt.xml files. I hadn't thought of this use case, so I'm not sure if it's fair to tell people to restrict their permutation or if we need to find a better way. Thoughts? Does this mean that we expect all projects to already be confined to one permutation, either via set-property or collapse-all-permutations? Is there no way to achieve that synthetically? Further, does this mean that one cannot test in multiple browsers simultaneously, for example re-compiling in FF until some behavior is satisfactory, then moving to Chrome (at least without stopping and restarting SDM)? -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/cdf99604-44c9-41b5-9cca-4f45227a3c89%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/cdf99604-44c9-41b5-9cca-4f45227a3c89%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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6fovE52iouAswSHFpQ8dp1sLZYDTUmqBD--bhtvC0akg%40mail.gmail.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D6fovE52iouAswSHFpQ8dp1sLZYDTUmqBD--bhtvC0akg%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/9f2df599-8c4b-47dd-b41e-ba3b96afc3cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) best, Robert On Tuesday, September 30, 2014 8:53:22 PM UTC+2, John Stalcup wrote: I can explain what's going here I think. Incremental compile is made possible by storing and reusing data in a new object called a MinimalRebuildCache. Since some of the analysis that incremental compilation is much simpler when there is only one permutation being compiled and since the contents of a MinimalRebuildCache instance are specific to a single permutation we decided to put in a requirement that when compiling incrementally the compiler be invoked with a binding property set that restricts permutations to just 1. To make sure this worked out fine for everyone we also turn on the -noPrecompile option so that all compiles are triggered from the browser, which ensures that the binding property set is specific to a single permutation. I'm not completely aware of your configuration but... it appears that you're using incremental compiles from a test runner, and this test runner isn't restricting the permutations to just 1. And that is being caught by an assertion. You can fix this by adding some set-property tags to your test .gwt.xml files. I hadn't thought of this use case, so I'm not sure if it's fair to tell people to restrict their permutation or if we need to find a better way. Thoughts? John On Tue, Sep 30, 2014 at 11:31 AM, Brandon Donnelson branfl...@gmail.com javascript: wrote: I'm not sure whats going on yet, but I've got some recompile issue coming up when trying to start dev mode. (This isn't using in browser recompile button) After moving to Java 1.7 because of a Java 1.6 error I got stuck with this error. Not sure whats going on yet, but I thought I'd post it for those who are interested. I've heard turning on and off dev mode fixes it. I'll test more later. Runing CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 1.7, -bindAddress, 127.0.0.1, -logLevel, INFO, com.sencha.gxt.test.TestRunner] Super Dev Mode starting up workDir: /var/folders/x8/9wz7qtw96t7grkdyjw1l61p4gn/T/gwt-codeserver-362446698832754749.tmp Loading Java files in com.sencha.gxt.test.TestRunner. Ignored 90 units with compilation errors in first pass. Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors. To compile the module 'testrunner' , visit: http://127.0.0.1:9876/recompile/testrunner?user.agent=safari Module setup completed in 5256 ms The code server is ready. Next, visit: http://127.0.0.1:9876/ GET /recompile/testrunner Job com.sencha.gxt.test.TestRunner_1_0 starting job: com.sencha.gxt.test.TestRunner_1_0 binding: user.agent=safari Compiling module com.sencha.gxt.test.TestRunner [ERROR] Current binding properties are expanding to more than one permutation but per-file compilation requires that each compile operate on only one permutation. [WARN] recompile failed [WARN] continuing to serve previous version -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/90b99fa9-e7f2-4908-ad36-28b775f24edb%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/90b99fa9-e7f2-4908-ad36-28b775f24edb%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/96381a83-8902-43f0-b39b-47bfef77f8b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/164ed8aa-8c93-4954-a293-a0656ffbf981%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
Is it ok? 9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js gxt.user.agent chrome user.agent safari user.agent.os linux 9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js gxt.user.agent chrome user.agent safari user.agent.os mac 9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js gxt.user.agent chrome user.agent safari user.agent.os unknown 9E2D25ADAB9D44AFEFC3E887DE3E3116.cache.js gxt.user.agent chrome user.agent safari user.agent.os windows Devmode:devmode.js -- 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/758b2ecb-a3ac-4caf-9c9d-928d01a545ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
@thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/54806774.6070106%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
I'm seeing this file in the artefacts generated by the SDM compile in the temp dir. Isn't editing this file only going to apply to the current invocation though? Presumably next time around it's going to get a different temp dir, and this fill will get recreated again. Have to confess - I don't fully follow what this file does though, and why we need to manually edit it On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: @thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/a02ba7ee-3bf6-4153-a256-b572e20c21e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
The mappings file only reports what was going on in the compile phase, so modifying it has no effect. You have to set specific values for your properties in the module.xml files: e.g. set-property name=user.agent value=safari/ SDM picks this change up I believe without restart. However to see the change in the mappings file too, you have to clean and recompile (i.e. start your devserver). On 04/12/14 15:02, Rob Walker wrote: I'm seeing this file in the artefacts generated by the SDM compile in the temp dir. Isn't editing this file only going to apply to the current invocation though? Presumably next time around it's going to get a different temp dir, and this fill will get recreated again. Have to confess - I don't fully follow what this file does though, and why we need to manually edit it On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: @thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/54806A58.9070203%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
OK - I know I'm being exceptionally dumb here, but won't that also limit a production build to that 1 permutation? On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote: The mappings file only reports what was going on in the compile phase, so modifying it has no effect. You have to set specific values for your properties in the module.xml files: e.g. set-property name=user.agent value=safari/ SDM picks this change up I believe without restart. However to see the change in the mappings file too, you have to clean and recompile (i.e. start your devserver). On 04/12/14 15:02, Rob Walker wrote: I'm seeing this file in the artefacts generated by the SDM compile in the temp dir. Isn't editing this file only going to apply to the current invocation though? Presumably next time around it's going to get a different temp dir, and this fill will get recreated again. Have to confess - I don't fully follow what this file does though, and why we need to manually edit it On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: @thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
I am really curious why this is not working for you in the first place. Since the code we added to SDM should always scope you down to one permutation. Are you still using bookmarklets? (These do not deal with this properly and should not be used anymore). On Thu, Dec 4, 2014 at 3:43 PM, Rob Walker piste.shred...@googlemail.com wrote: OK - I know I'm being exceptionally dumb here, but won't that also limit a production build to that 1 permutation? On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote: The mappings file only reports what was going on in the compile phase, so modifying it has no effect. You have to set specific values for your properties in the module.xml files: e.g. set-property name=user.agent value=safari/ SDM picks this change up I believe without restart. However to see the change in the mappings file too, you have to clean and recompile (i.e. start your devserver). On 04/12/14 15:02, Rob Walker wrote: I'm seeing this file in the artefacts generated by the SDM compile in the temp dir. Isn't editing this file only going to apply to the current invocation though? Presumably next time around it's going to get a different temp dir, and this fill will get recreated again. Have to confess - I don't fully follow what this file does though, and why we need to manually edit it On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: @thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Google Germany GmbH *Dienerstr. 12* *80331 München* Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens -- 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/CALLujiqzLC%3D7bfeqfC3KWL2U%2Bxd_WJTZE8_Jzck4oRxgQh4Twg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
It would. So I have a common.gwt.xml which a Dev.gwt.xml inherits and restricts (as discussed in this topic). The production.gwt.xml also inherits from common but without restrictions. In such or similar setup you can also keep other dev specific stuff separated, logging etc. On December 4, 2014 3:43:11 PM GMT+01:00, Rob Walker piste.shred...@googlemail.com wrote: OK - I know I'm being exceptionally dumb here, but won't that also limit a production build to that 1 permutation? On Thursday, 4 December 2014 16:06:23 UTC+2, Robert Hoffmann wrote: The mappings file only reports what was going on in the compile phase, so modifying it has no effect. You have to set specific values for your properties in the module.xml files: e.g. set-property name=user.agent value=safari/ SDM picks this change up I believe without restart. However to see the change in the mappings file too, you have to clean and recompile (i.e. start your devserver). On 04/12/14 15:02, Rob Walker wrote: I'm seeing this file in the artefacts generated by the SDM compile in the temp dir. Isn't editing this file only going to apply to the current invocation though? Presumably next time around it's going to get a different temp dir, and this fill will get recreated again. Have to confess - I don't fully follow what this file does though, and why we need to manually edit it On Thursday, 4 December 2014 15:54:48 UTC+2, Robert Hoffmann wrote: @thomas thank you, that helped me to reduce the permutations to one. For the record, compilation-mappings.txt contained multiple cache.js file entries, now it only contains one FC8BCE744D2BA8E0C463CE0D2F389DB7.cache.js Devmode:devmode.js ...and now sdm works. And it's fast :-) On Thursday, December 4, 2014 10:15:36 AM UTC+1, Robert Hoffmann wrote: Hi, Is there a way to see which properties cause the permutations? (I'm using GWT 2.7.0) When compiling your project, you should have a compilation-mappings.txt file generated next to the *.nocache.js. -- 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/5lgtM77-1tM/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/c32c04e2-0ea0-45fc-9e54-c86098d48d85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. _ Robert Hoffmann, Ph.D. _ +43 (0) 660 348 6095 robert.hoffmann@gmail.com _ -- 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/C0EC26FD-8F0A-44CB-9422-F247440952C0%40gmail.com. For more options, visit https://groups.google.com/d/optout.
