Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Jens, Thank you. Now it's working. SDM documentation should really be updated - http://www.gwtproject.org/articles/superdevmode.html Regards, Matic On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote: Instead of -workDir you should use -launcherDir which contains all public resources (from your public folders) as well as the generated nocache.js file. -workDir is just for temporary files for each recompile. If you use DevMode class instead of CodeServer then the DevMode class configures -launcherDir to the same value as DevMode -war. -- J. -- 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/4ed14921-e5b5-49e8-9426-ebb22a967b21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
I added a tracking item for updating SDM docs before 2.7.0 On Fri, Oct 31, 2014 at 8:00 AM, Matic Petek maticpe...@gmail.com wrote: Jens, Thank you. Now it's working. SDM documentation should really be updated - http://www.gwtproject.org/articles/superdevmode.html Regards, Matic On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote: Instead of -workDir you should use -launcherDir which contains all public resources (from your public folders) as well as the generated nocache.js file. -workDir is just for temporary files for each recompile. If you use DevMode class instead of CodeServer then the DevMode class configures -launcherDir to the same value as DevMode -war. -- J. -- 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/4ed14921-e5b5-49e8-9426-ebb22a967b21%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/4ed14921-e5b5-49e8-9426-ebb22a967b21%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/CALLujipdrM%2BA1KPm6vrmzVYpU-XnJRCdBQE2b9MkZw3KA_5kKw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
With SDM, when using the -noserver argument. Do we have to manually run the SDM code server, and continue to use the bookmarklets? This would be helpful information in the docs also. On Friday, 31 October 2014 11:25:31 UTC, Daniel Kurka wrote: I added a tracking item for updating SDM docs before 2.7.0 On Fri, Oct 31, 2014 at 8:00 AM, Matic Petek matic...@gmail.com javascript: wrote: Jens, Thank you. Now it's working. SDM documentation should really be updated - http://www.gwtproject.org/articles/superdevmode.html Regards, Matic On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote: Instead of -workDir you should use -launcherDir which contains all public resources (from your public folders) as well as the generated nocache.js file. -workDir is just for temporary files for each recompile. If you use DevMode class instead of CodeServer then the DevMode class configures -launcherDir to the same value as DevMode -war. -- J. -- 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/4ed14921-e5b5-49e8-9426-ebb22a967b21%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/4ed14921-e5b5-49e8-9426-ebb22a967b21%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/b5160f02-b94a-4569-83e3-2f324b6db5b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
With SDM, when using the -noserver argument. Do we have to manually run the SDM code server, and continue to use the bookmarklets? DevMode -noserver means that no embedded Jetty server will be started to serve your war directory. It will still start the SDM CodeServer and put a special module.nocache.js file into your DevMode -war directory which supports recompiles on page refresh. So with -noserver you must deploy your app on your own. -- J. -- 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/f428c57c-8d4a-4f54-8a1c-98b471e87ca2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
On Friday, October 31, 2014 3:05:29 PM UTC+1, Jens wrote: With SDM, when using the -noserver argument. Do we have to manually run the SDM code server, and continue to use the bookmarklets? DevMode -noserver means that no embedded Jetty server will be started to serve your war directory. It will still start the SDM CodeServer and put a special module.nocache.js file into your DevMode -war directory which supports recompiles on page refresh. So with -noserver you must deploy your app on your own. In other words, DevMode with -noserver is the same as CodeServer with -launcherDir (and -noprecompile), with -launcherDir set to the same value as DevMode's -war. …then CodeServer with -launcherDir means the bookmarklets are no longer needed (provided your browser loads the *.nocache.js that's been generated into the -launcherDir) -- 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/48a4ddd8-d6f0-42da-8e2a-21ec13984fe5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- J -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.nehlme...@gmail.com wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- J -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/CADcXZMwR3WUSpEvVoGfW%2BYo%2B2LW_vMinRKJyxUsu4bW_hHROjQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Jens Colin Thank you for your help. The problem is really module.nocache.js file (or batter - generated js files), the behaviour is for my a litter strange : 1) my Ant file looks like this : target name=superdevmode_main depends=javac description=Run Super Dev Mode java failonerror=true fork=true classname=com.google.gwt.dev.codeserver.CodeServer ... arg value=-workDir/ arg value=./war/ arg value=com.mycompany.mymodule/ /java /target Because I set workDir parameter, I think at first startup I should get mymodule folder inside war folder and two basic files (metakockamain.nocache.js, metakockamain.recompile.nocache.js) for first startup. Unfortunately I still get temporary folder com.mycompany.mymodule/compile-1/ with expected files. No /war/mymodule/ folder. 2) OK, I manually copy com.mycompany.mymodule/compile-1/war/mymodule/* into /war/mymodule/ 3) We are using ImageBundle and we need image sprite files. That is why I copy com.mycompany.mymodule/compile-2/war/mymodule/* into /war/mymodule/ and now browser refresh has stop working. Two thinks in upper description does not compute for me : (1) why *.js files are not generated in workDir folder (3) if I copy *.js files from after increment compile folder into /war/mymodule/, whay browser refresh has stop working. Thank you, Regards, Matic On Thursday, October 30, 2014 4:43:14 PM UTC+1, Colin Alworth wrote: It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.ne...@gmail.com javascript: wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- J -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/e917eb3a-2c5d-4df2-b1fe-174e62f000c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: Upgrade 2.7 beta1 to rc1 - browser refresh and change detection not working
Jens Colin Thank you for your help. The problem is really module.nocache.js file (or batter - generated js files), the behaviour is for my a litter strange : 1) my Ant file looks like this : target name=superdevmode_main depends=javac description=Run Super Dev Mode java failonerror=true fork=true classname=com.google.gwt.dev.codeserver.CodeServer ... arg value=-workDir/ arg value=./war/ arg value=com.mycompany.mymodule/ /java /target Because I set workDir parameter, I think at first startup I should get mymodule folder inside war folder and two basic files (mymodule.nocache.js, mymodule.recompile.nocache.js) for first startup. Unfortunately I still get temporary folder com.mycompany.mymodule/compile-1/ with expected files. No /war/mymodule/ folder. 2) OK, I manually copy com.mycompany.mymodule/compile-1/war/mymodule/* into /war/mymodule/ 3) We are using ImageBundle and we need image sprite files. That is why I copy com.mycompany.mymodule/compile-2/war/mymodule/* into /war/mymodule/ and now browser refresh has stop working. Two thinks in upper description does not compute for me : (1) why *.js files are not generated in workDir folder (3) if I copy *.js files from after increment compile folder into /war/mymodule/, whay browser refresh has stop working. Thank you, Regards, Matic On Thursday, October 30, 2014 4:43:14 PM UTC+1, Colin Alworth wrote: It is also possible that there is a stale copy of .java resources on your classpath, such as in target/classes/ for a maven project - we've seen that get in the way as well. Make sure that either target/classes/ isn't on your classpath, or that it doesn't have another (stale) copy of whatever you are trying to compile. On Thu Oct 30 2014 at 10:40:52 AM Jens jens.ne...@gmail.com javascript: wrote: I assume you have deployed an old module.nocache.js file. Try a clean start by deleting your /war/modulename folder and restart DevMode. A new module.nocache.js file should be generated (could take a bit as the CodeServer needs to start before this file gets generated) which automatically recompiles your app each time you refresh the browser. -- J -- 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/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/0254ed3a-fbff-4b8f-b7f3-31997d32c2d4%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/a6055f65-85f6-483c-9db0-832d8e19ea17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
