On Monday, March 7, 2016 at 4:08:37 PM UTC+1, Stefan Falk wrote: > > I already have a project of type gwt-maven-archetypes. I don't want to > change the whole project to another archetype. >
Why would you "change the whole project to another archetype"? An archetype is only a skeleton-generator; the doc talks about the provided appengine archetype to make it easier for people knowing relatively few things about Maven; but that doesn't mean you *have* to use the archetypes. > > On Sunday, 6 March 2016 21:16:22 UTC+1, Greg wrote: >> >> >> https://cloud.google.com/appengine/docs/java/tools/maven#uploading_your_app_to_production_app_engine >> > >From what I read here, you'd do something like: mvn install (to make your shared and client artifacts available to the server one outside the reactor build) cd *-server && mvn appengine:update Of course, that's after you configured the appengine-maven-plugin in the *-server project's POM. Otherwise, the tool seems to be the com.google.appengine.tools.admin.AppCfg class in the appengine-tools-api.jar from the AppEngine SDK, that you'd call with the "update" command and your WAR file (or exploded WAR directory, i.e. *-server/target/*-server-*/ after a "mvn package", I can't tell) as arguments. (note: it took me 10 minutes to find that information from the Maven and Ant documentation pages and a bit of googling; I never used AppEngine) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
