Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
But i cannot limit this in the production rite.. i can limit it during my development.I have used collapse-all-properties/ which had resolved my issue and there is only one permutation happening.But i want to know will there be any disadvantages or any side effects by using it. On Wednesday, 6 May 2015 01:33:14 UTC+5:30, Robert Hoffmann wrote: Limit your permutations by being more stringent, e.g. set-property name=user.agent value=safari / On May 5, 2015 3:26:56 PM GMT+02:00, Kishore Palakollu kishorep...@gmail.com javascript: wrote: Hi Robert, i m facing the same issue. can you please tell me what has fixed your issue. My compilation-mappings.txt contains B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent gecko1_8 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie10 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie9 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent safari Devmode:devmode.js Thanks Regards, kishore. On Thursday, 4 December 2014 19:24:48 UTC+5:30, 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. _ Robert Hoffmann, Ph.D. _ +43 (0) 660 348 6095 robert.ho...@gmail.com javascript: _ -- 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/f64f8070-728a-4165-883d-4ccb87d0b765%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
Right, for production you should not do this, but then in production mode you will not need superdev. (Once the extend superdev to deal with this situation you can use superdev for both compilations) It helps if you use different gwt.xml files for production and dev (they could share a common inheritance.gwt.xml) On 06/05/15 13:27, Kishore Palakollu wrote: But i cannot limit this in the production rite.. i can limit it during my development.I have used collapse-all-properties/ which had resolved my issue and there is only one permutation happening.But i want to know will there be any disadvantages or any side effects by using it. On Wednesday, 6 May 2015 01:33:14 UTC+5:30, Robert Hoffmann wrote: Limit your permutations by being more stringent, e.g. set-property name=user.agent value=safari / On May 5, 2015 3:26:56 PM GMT+02:00, Kishore Palakollu kishorep...@gmail.com javascript: wrote: Hi Robert, i m facing the same issue. can you please tell me what has fixed your issue. My compilation-mappings.txt contains B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent gecko1_8 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie10 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie9 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent safari Devmode:devmode.js Thanks Regards, kishore. On Thursday, 4 December 2014 19:24:48 UTC+5:30, 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. _ Robert Hoffmann, Ph.D. _ +43 (0) 660 348 6095 robert.ho...@gmail.com javascript: _ -- 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 mailto: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/f64f8070-728a-4165-883d-4ccb87d0b765%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/f64f8070-728a-4165-883d-4ccb87d0b765%40googlegroups.com?utm_medium=emailutm_source=footer. 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/554A04AD.704%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
Hi Robert, i m facing the same issue. can you please tell me what has fixed your issue. My compilation-mappings.txt contains B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent gecko1_8 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie10 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie9 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent safari Devmode:devmode.js Thanks Regards, kishore. On Thursday, 4 December 2014 19:24:48 UTC+5:30, 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/bcf4a9ce-75f7-40af-a8c0-05273db066ee%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
Balázs, the js.embedded.properties configuration property might help here. Try adding extend-configuration-property name=js.embedded.properties value=my.platform / to your gwt.xml file On Tue, May 5, 2015 at 6:26 AM, Kishore Palakollu kishorepalako...@gmail.com wrote: Hi Robert, i m facing the same issue. can you please tell me what has fixed your issue. My compilation-mappings.txt contains B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent gecko1_8 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie10 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie9 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent safari Devmode:devmode.js Thanks Regards, kishore. On Thursday, 4 December 2014 19:24:48 UTC+5:30, 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/bcf4a9ce-75f7-40af-a8c0-05273db066ee%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/bcf4a9ce-75f7-40af-a8c0-05273db066ee%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/CAC7T7g%3DgxjSsQ8moFkszusQE_oNdT4yLwGBqdSyiYJGpM96Jcg%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
Limit your permutations by being more stringent, e.g. set-property name=user.agent value=safari / On May 5, 2015 3:26:56 PM GMT+02:00, Kishore Palakollu kishorepalako...@gmail.com wrote: Hi Robert, i m facing the same issue. can you please tell me what has fixed your issue. My compilation-mappings.txt contains B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent gecko1_8 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie10 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent ie9 B5079040E7FF0E555046C1AD8B647A66.cache.js locale en_EN user.agent safari Devmode:devmode.js Thanks Regards, kishore. On Thursday, 4 December 2014 19:24:48 UTC+5:30, 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/bcf4a9ce-75f7-40af-a8c0-05273db066ee%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/3511E94D-A11C-4481-912A-526C1AD6FD7E%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 see others note the Dev Mode On / Off cause this - what's the new approach then to enter Super Dev Mode? On Thursday, 4 December 2014 16:49:56 UTC+2, Daniel Kurka wrote: 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.s...@googlemail.com javascript: 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 javascript:. 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/e6e9f8cc-f976-4af5-baa4-a906fb9cc9c4%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
OK - this is very confusing, I went back to the Release Notes to see if I missed a breaking change in this area, but the 2.7.0RC1 release notes still reference the bookmarklets: *The Dev Mode On bookmarklet dialog shows whether Super Dev Mode is turned on for each module on the page.* And they don't suggest a different approacH is needed - or maybe I'm just not seeing it in the Docs -- Rob On Friday, 5 December 2014 10:33:18 UTC+2, Rob Walker wrote: I see others note the Dev Mode On / Off cause this - what's the new approach then to enter Super Dev Mode? On Thursday, 4 December 2014 16:49:56 UTC+2, Daniel Kurka wrote: 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). -- 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/93745440-779b-4877-b852-c689e6b1721a%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'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it. Reading the docs on Debugging, they do kind of explain this - but there are places where they reference what appears to be the original way of running Super Dev Mode using bookmarklets, As above, those of us using these are not finding they work. Also, for us, we don't run the embedded Jetty so need to run standalone server. Falling back to our old Dev Mode launch script, it does try to launch Super Dev Mode but aborts with an error: Super Dev Mode starting up workDir: C:\Temp\gwt-codeserver-8197845274977519094.tmp Loading Java files in GwtApiTas. * Ignored 308 units with compilation errors in first pass.* Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors. Module setup completed in 4878 ms Loading Java files in VtWebUi. * Ignored 310 units with compilation errors in first pass.* Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors. Resolving com.ascert.tas.gwtapi.client.driverlib.DriverlibService Found type 'com.ascert.tas.gwtapi.client.driverlib.DriverlibService' Resolving method getDriverDescriptor [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method getPackagedEnvironments [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method getRepositories [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckReturn Resolving method refreshRepository [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method deletePackages [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method downloadPackages [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method pinPackage [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Resolving method unpinPackages [WARN] Ignoring unresolvable annotation type com.ascert.tas.gwtapi.c lient.security.VtasSecurityCheckMethod Finding entry point classes * [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 entri* *es properly* We don't have 600 sources with errors, since it clean compiles and runs fine. So I'm guessing it has something to do with source paths, given the number of modules skipped with errors. But at this stage I'm still lost. Overall this was not a well documented or explained transition! I am really not surprised the average users are battling with it -- 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/7141631c-513b-4a58-8d0f-39098bff646d%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 Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote: I'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it. …or you can keep your launcher with CodeServer but add a -launcherDir argument pointing to the folder your standalone server is serving. CodeServer will then generate a .nocache.js in there that enables compile on load. And yes the docs need an update (and I wasn't even aware of the issue with the bookmarklets; good to know, and I believe we should try to fix it because it can be really handy) -- 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/b4a63e66-0378-4e66-a7e1-219cf4d1a891%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
OK, so after a bit of a battle, I can get Dev Mode to run under 2.7, which now of course launches Super Dev Mode I needed to change some things though. Our original launch command looked like this: ava -cp *%TAS_HOME%/proj/webui/src/com/ascert/webui/vt*; *%TAS_HOME%/proj/tas/gwtapi/src/com/ascert/tas/gwtapi*; *%TAS_HOME%/proj/tas/gwtapi/src*;*%TAS_HOME%/proj/webui/src*;%TAS_HOME%/build/ext/gwt-user.jar;%TAS_HOME%/proj/webui/lib/gwt-servlet-deps.jar;%TAS_HOME%/build/ext/gwt-dev.jar;%TAS_HOME%/build/ext/validation-api-1.0.0.GA-sources.jar;%TAS_HOME%/build/ext/gwtext.jar;%TAS_HOME%/build/ext/gwtextux.jar;%TAS_HOME%/build/ext/highcharts.jar;%TAS_HOME%/build/ext/gxt.jar;%TAS_HOME%/build/ext/gxt-chart.jar;%TAS_HOME%/build/ext/gxt-legacy.jar com.google.gwt.dev.DevMode -noserver -startupUrl http://localhost:8084/VtWebUi/VtWebUi.html* GwtApiTas VtWebUi * I forget why, but we needed paths to both the GWT XML and the sources separately. SDM under 2.7 does not like this, instead we needed to fully qualify our GWT XML with package names, and remove the path entry to them. In fact one module wasn't even on our original command which Dev Modes did not complain about (presumably because it was in same source path as main module) java -cp *%TAS_HOME%/proj/tas/gwtapi/src*;*%TAS_HOME%/proj/webui/src*;%TAS_HOME%/build/ext/gwt-user.jar;%TAS_HOME%/proj/webui/lib/gwt-servlet-deps.jar;%TAS_HOME%/build/ext/gwt-dev.jar;%TAS_HOME%/build/ext/validation-api-1.0.0.GA-sources.jar;%TAS_HOME%/build/ext/gwtext.jar;%TAS_HOME%/build/ext/gwtextux.jar;%TAS_HOME%/build/ext/highcharts.jar;%TAS_HOME%/build/ext/gxt.jar;%TAS_HOME%/build/ext/gxt-chart.jar;%TAS_HOME%/build/ext/gxt-legacy.jar com.google.gwt.dev.DevMode -nostartServer -logLevel TRACE -startupUrl http://localhost:8084/VtWebUi/VtWebUi.html *com.ascert.tas.gwtapi.GwtApiTas* *com.ascert.webui.core.GwtComponents* *com.ascert.webui.vt.VtWebUi* This removed the 600+ sources with errors, but we still hit an error with one of our sub-module missing an inhertis: When we compile GWT normally, we don't see this error - presumably because that module is inherited by our main module. Not sure yet if this is fully working, but it is at least launching into Super Dev Mode via the Dev Mode command line -- 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/94f3573f-4aaf-427c-9bdc-b1cd86198cd5%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
Sadly the -launcherDir won't work for us I don't think - we're running an embedded Felix/OSGi server which serves up our application from bundle JARS. So there is no dir we can point them at. As per thread below, I think I am making progress with Dev Mode launch though - at least it is actually launching now anyhow. Seemed to need quite a few command line mods from our original BAT file to launch Dev Mode On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote: On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote: I'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it. …or you can keep your launcher with CodeServer but add a -launcherDir argument pointing to the folder your standalone server is serving. CodeServer will then generate a .nocache.js in there that enables compile on load. And yes the docs need an update (and I wasn't even aware of the issue with the bookmarklets; good to know, and I believe we should try to fix it because it can be really handy) -- 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/1d9b9b6e-07f1-4c35-96d6-bdc3aa471267%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
Nope - even though Dev Mode runs now and goes into Super Dev Mode, our application is not actually loading in SDM when we visit the web page. Our web serving and resources are bundled into JARs, so I suspect the idea of overwriting the .nocache.js is just flawed or not working for this mode. There is no .nocache.js existing in the file system which overwriting will change our application behaviour. SDM does still work for us if run explicitly, but we have to add a -noincremental flag, which I think defeats any speed gains On Friday, 5 December 2014 11:42:48 UTC+2, Rob Walker wrote: Sadly the -launcherDir won't work for us I don't think - we're running an embedded Felix/OSGi server which serves up our application from bundle JARS. So there is no dir we can point them at. As per thread below, I think I am making progress with Dev Mode launch though - at least it is actually launching now anyhow. Seemed to need quite a few command line mods from our original BAT file to launch Dev Mode On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote: On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote: I'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it. …or you can keep your launcher with CodeServer but add a -launcherDir argument pointing to the folder your standalone server is serving. CodeServer will then generate a .nocache.js in there that enables compile on load. And yes the docs need an update (and I wasn't even aware of the issue with the bookmarklets; good to know, and I believe we should try to fix it because it can be really handy) -- 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/fd93475e-ac71-4455-824a-a46d87d5e3c1%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 Rob, I'm using Jboss Fuse which uses Felix and it works fine in SuperDevMode. But did I read it right that you start the osgi container embedded with superdevmode ? I would love to know how I can achieve that as well because then I don't need to use the -noserver parameter anymore. I am using the bookmarklets to force a compile and enforce superdevmode with the remote server. That works just fine for me. On Fri, Dec 5, 2014 at 10:42 AM, Rob Walker piste.shred...@googlemail.com wrote: Sadly the -launcherDir won't work for us I don't think - we're running an embedded Felix/OSGi server which serves up our application from bundle JARS. So there is no dir we can point them at. As per thread below, I think I am making progress with Dev Mode launch though - at least it is actually launching now anyhow. Seemed to need quite a few command line mods from our original BAT file to launch Dev Mode On Friday, 5 December 2014 11:31:55 UTC+2, Thomas Broyer wrote: On Friday, December 5, 2014 10:00:59 AM UTC+1, Rob Walker wrote: I'm really not surprise people are hitting this issue. It's not clear (or wasn't to me) from the Release Notes that you no longer run Super Dev Mode from the standalone program in 2.7 as was done in 2.6, but that running via Dev Mode enables it. …or you can keep your launcher with CodeServer but add a -launcherDir argument pointing to the folder your standalone server is serving. CodeServer will then generate a .nocache.js in there that enables compile on load. And yes the docs need an update (and I wasn't even aware of the issue with the bookmarklets; good to know, and I believe we should try to fix it because it can be really handy) -- 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/1d9b9b6e-07f1-4c35-96d6-bdc3aa471267%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/1d9b9b6e-07f1-4c35-96d6-bdc3aa471267%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/CABrJHW1bvqdnq2p%3D1X%3DrQw43S5%2BSH27USnFE3vM0fcr3M0RT-w%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
In fact - it does seem to work in both models, but only with the following: - I have to use the Dev Mod On bookmarklet to trigger a recompile. If I just reload, it doesn't seem to detect and recompile on it's own. I have a feeling running SDM directly did do a recompile on reload on one occasion, but can't be sure. - I have to use a -noincremental command option. Without this I get the too many permutations error still -- 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/4756a6b3-1c1a-4454-a1b9-7cbf7afc7ec2%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.
Re: [gwt-contrib] Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
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 niloc...@gmail.com 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. 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. 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. 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
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.dram...@gmail.com 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 niloc...@gmail.com 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. 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. 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/CAFw3gJ8iBDL7p9FObj2F0ax0N9bQ15iSdi2cY4_WOKOKyO%2BKSA%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
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 branflake2...@gmail.com 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. 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/CAFw3gJ9b%3Dp_H-DfdqmvjkYUOVWTn699hkQPGMejaZmLpsH%3DCzA%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
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. 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. For more options, visit https://groups.google.com/d/optout.
