Re: [google-appengine] Re: Testing GWT + GAE locally (not DevMode)
Hi Jeff, how's it going with Motomapia? Anyway, yah, that should be the case, however, the App i'm trying to push is just a test app, since i'm not finished with the app... I just needed to check how it will look like and behave in the GAE runtime. Where when I found something that the SDK runtime was able to miss. Cheers! On Wed, May 1, 2013 at 10:41 PM, Jeff Schnitzer wrote: > FWIW, we nearly always deploy to a sandbox appid and test before deploying > to production. > > Jeff > > > On Wed, May 1, 2013 at 3:04 AM, xybrek wrote: > >> Issue resolved by following this blog article: >> >> >> http://bpossolo.blogspot.com/2013/01/the-ultimate-guide-to-gwt-gae-maven.html >> >> and the maven command allowed the app to deploy (with GWT) to GAE cloud: >> appengine:update >> >> >> On Wednesday, May 1, 2013 1:13:26 PM UTC+8, xybrek wrote: >>> >>> Hmmm... that could be the problem, when deploying I use the *appcfg.cmd >>> update "path/to/war" * >>> Do you mean I need to upload/update through the maven plugin? I just use >>> maven for local deployment: like "mvn *gwt:run*" >>> >>> Will this command mvn *gae*:*deploy *deploy to GAE as well as compile >>> GWT? I'm thinking that this is analogous to *mvn gae:ru*n that does not >>> involved the GWT side of things? >>> >>> Xybrek >>> >>> On Wednesday, May 1, 2013 12:52:26 PM UTC+8, Brandon Donnelson wrote: When deploying does the GWT module compile before it deploys? It should compile before it deploys. Another option to verify its compiling is delete the gwt project module and related from the war directory, thats compiled, before deploying. (Don't delete any static resources.) Is the compile comping the module getting deployed, or is there more than one module and one module is not getting compiled. There are a few other reasons that this happens, but maybe that hints at helping deployments. Brandon On Tuesday, April 30, 2013 1:58:06 PM UTC-7, xybrek wrote: > > `DevMode` works just fine when testing a GWT + GAE application. > However the problem arises when we try to deploy our app in GAE cloud, and > suddenly we get: > > > GWT module 'app' need to be recompiled > > After a long update/upload time. The issue now is how can we test > locally and be sure at least that we won't suddenly get this error. In a > typical GWT (non-GAE) its very easy to do, just deploy it to a local > Tomcat > of JBoss AS server. > > However we can't do this for a GAE app. So what are the options to > achieve this? > > - Where to deploy a GWT+GAE app to be able to see if the GWT needs to > be recompiled or what, before we even try to upload it. > - Or are there any better way? `SuperDevMode` perhaps? > -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to google-appengine+unsubscr...@googlegroups.com. >> >> To post to this group, send email to google-appengine@googlegroups.com. >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-appengine/thev4M1M_WY/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, send an email to > google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Testing GWT + GAE locally (not DevMode)
FWIW, we nearly always deploy to a sandbox appid and test before deploying to production. Jeff On Wed, May 1, 2013 at 3:04 AM, xybrek wrote: > Issue resolved by following this blog article: > > > http://bpossolo.blogspot.com/2013/01/the-ultimate-guide-to-gwt-gae-maven.html > > and the maven command allowed the app to deploy (with GWT) to GAE cloud: > appengine:update > > > On Wednesday, May 1, 2013 1:13:26 PM UTC+8, xybrek wrote: >> >> Hmmm... that could be the problem, when deploying I use the *appcfg.cmd >> update "path/to/war" * >> Do you mean I need to upload/update through the maven plugin? I just use >> maven for local deployment: like "mvn *gwt:run*" >> >> Will this command mvn *gae*:*deploy *deploy to GAE as well as compile >> GWT? I'm thinking that this is analogous to *mvn gae:ru*n that does not >> involved the GWT side of things? >> >> Xybrek >> >> On Wednesday, May 1, 2013 12:52:26 PM UTC+8, Brandon Donnelson wrote: >>> >>> When deploying does the GWT module compile before it deploys? It should >>> compile before it deploys. Another option to verify its compiling is delete >>> the gwt project module and related from the war directory, thats compiled, >>> before deploying. (Don't delete any static resources.) Is the compile >>> comping the module getting deployed, or is there more than one module and >>> one module is not getting compiled. There are a few other reasons that this >>> happens, but maybe that hints at helping deployments. >>> >>> Brandon >>> >>> On Tuesday, April 30, 2013 1:58:06 PM UTC-7, xybrek wrote: `DevMode` works just fine when testing a GWT + GAE application. However the problem arises when we try to deploy our app in GAE cloud, and suddenly we get: GWT module 'app' need to be recompiled After a long update/upload time. The issue now is how can we test locally and be sure at least that we won't suddenly get this error. In a typical GWT (non-GAE) its very easy to do, just deploy it to a local Tomcat of JBoss AS server. However we can't do this for a GAE app. So what are the options to achieve this? - Where to deploy a GWT+GAE app to be able to see if the GWT needs to be recompiled or what, before we even try to upload it. - Or are there any better way? `SuperDevMode` perhaps? >>> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Testing GWT + GAE locally (not DevMode)
Issue resolved by following this blog article: http://bpossolo.blogspot.com/2013/01/the-ultimate-guide-to-gwt-gae-maven.html and the maven command allowed the app to deploy (with GWT) to GAE cloud: appengine:update On Wednesday, May 1, 2013 1:13:26 PM UTC+8, xybrek wrote: > > Hmmm... that could be the problem, when deploying I use the *appcfg.cmd > update "path/to/war" * > Do you mean I need to upload/update through the maven plugin? I just use > maven for local deployment: like "mvn *gwt:run*" > > Will this command mvn *gae*:*deploy *deploy to GAE as well as compile > GWT? I'm thinking that this is analogous to *mvn gae:ru*n that does not > involved the GWT side of things? > > Xybrek > > On Wednesday, May 1, 2013 12:52:26 PM UTC+8, Brandon Donnelson wrote: >> >> When deploying does the GWT module compile before it deploys? It should >> compile before it deploys. Another option to verify its compiling is delete >> the gwt project module and related from the war directory, thats compiled, >> before deploying. (Don't delete any static resources.) Is the compile >> comping the module getting deployed, or is there more than one module and >> one module is not getting compiled. There are a few other reasons that this >> happens, but maybe that hints at helping deployments. >> >> Brandon >> >> On Tuesday, April 30, 2013 1:58:06 PM UTC-7, xybrek wrote: >>> >>> `DevMode` works just fine when testing a GWT + GAE application. However >>> the problem arises when we try to deploy our app in GAE cloud, and suddenly >>> we get: >>> >>> >>> GWT module 'app' need to be recompiled >>> >>> After a long update/upload time. The issue now is how can we test >>> locally and be sure at least that we won't suddenly get this error. In a >>> typical GWT (non-GAE) its very easy to do, just deploy it to a local Tomcat >>> of JBoss AS server. >>> >>> However we can't do this for a GAE app. So what are the options to >>> achieve this? >>> >>> - Where to deploy a GWT+GAE app to be able to see if the GWT needs to >>> be recompiled or what, before we even try to upload it. >>> - Or are there any better way? `SuperDevMode` perhaps? >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Testing GWT + GAE locally (not DevMode)
Hmmm... that could be the problem, when deploying I use the *appcfg.cmd update "path/to/war" * Do you mean I need to upload/update through the maven plugin? I just use maven for local deployment: like "mvn *gwt:run*" Will this command mvn *gae*:*deploy *deploy to GAE as well as compile GWT? I'm thinking that this is analogous to *mvn gae:ru*n that does not involved the GWT side of things? Xybrek On Wednesday, May 1, 2013 12:52:26 PM UTC+8, Brandon Donnelson wrote: > > When deploying does the GWT module compile before it deploys? It should > compile before it deploys. Another option to verify its compiling is delete > the gwt project module and related from the war directory, thats compiled, > before deploying. (Don't delete any static resources.) Is the compile > comping the module getting deployed, or is there more than one module and > one module is not getting compiled. There are a few other reasons that this > happens, but maybe that hints at helping deployments. > > Brandon > > On Tuesday, April 30, 2013 1:58:06 PM UTC-7, xybrek wrote: >> >> `DevMode` works just fine when testing a GWT + GAE application. However >> the problem arises when we try to deploy our app in GAE cloud, and suddenly >> we get: >> >> >> GWT module 'app' need to be recompiled >> >> After a long update/upload time. The issue now is how can we test locally >> and be sure at least that we won't suddenly get this error. In a typical >> GWT (non-GAE) its very easy to do, just deploy it to a local Tomcat of >> JBoss AS server. >> >> However we can't do this for a GAE app. So what are the options to >> achieve this? >> >> - Where to deploy a GWT+GAE app to be able to see if the GWT needs to be >> recompiled or what, before we even try to upload it. >> - Or are there any better way? `SuperDevMode` perhaps? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Testing GWT + GAE locally (not DevMode)
When deploying does the GWT module compile before it deploys? It should compile before it deploys. Another option to verify its compiling is delete the gwt project module and related from the war directory, thats compiled, before deploying. (Don't delete any static resources.) Is the compile comping the module getting deployed, or is there more than one module and one module is not getting compiled. There are a few other reasons that this happens, but maybe that hints at helping deployments. Brandon On Tuesday, April 30, 2013 1:58:06 PM UTC-7, xybrek wrote: > > `DevMode` works just fine when testing a GWT + GAE application. However > the problem arises when we try to deploy our app in GAE cloud, and suddenly > we get: > > > GWT module 'app' need to be recompiled > > After a long update/upload time. The issue now is how can we test locally > and be sure at least that we won't suddenly get this error. In a typical > GWT (non-GAE) its very easy to do, just deploy it to a local Tomcat of > JBoss AS server. > > However we can't do this for a GAE app. So what are the options to achieve > this? > > - Where to deploy a GWT+GAE app to be able to see if the GWT needs to be > recompiled or what, before we even try to upload it. > - Or are there any better way? `SuperDevMode` perhaps? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
