Would that work for an already existing project? My problem is this: https://code.google.com/p/googleappengine/issues/detail?can=2&start=0&num=100&q=Execution%20default&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log&groupby=&sort=&id=12804
at the moment. appengine is either against me or I am doing something wrong and I can't figure out what.. BR; Stefan On Tuesday, 8 March 2016 17:58:17 UTC+1, Rogelio Flores wrote: > > I started my gwt + appengine project with Brandon's archetype which > already does everything for me: > > > https://github.com/branflake2267/Archetypes/tree/master/archetypes/gwt-basic-rpc-appengine > > This uploads my app (after you build it as mentioned already in the thread) > > mvn appengine:update > > I don't think I changed many things in the pom.xml besides updating to the > latest appengine SDK. At minimum, you can take a look at the pom.xml file > to know how to configure it all. > > > On Monday, March 7, 2016 at 8:49:21 AM UTC-7, Stefan Falk wrote: >> >> Ah sorry, I saw that too late. >> >> Well, okay so my assumption was right. What I did was placing the plugin >> into the pom.xml of my myapp-server module: >> >> <plugin> >> <groupId>com.google.appengine</groupId> >> <artifactId>appengine-maven-plugin</artifactId> >> <version>${appengine.version}</version> >> <configuration> >> <enableJarClasses>false</enableJarClasses> >> <version>${app.version}</version> >> </configuration> >> </plugin> >> <plugin> >> <groupId>com.google.appengine</groupId> >> <artifactId>gcloud-maven-plugin</artifactId> >> <version>${gcloud.plugin.version}</version> >> <configuration> >> <set_default>true</set_default> >> </configuration> >> </plugin> >> >> If that is correct so far I think I should be able to make it work. At >> the moment though maven is complaining about that it can't find the plugin >> "appengine" .. >> >> On Monday, 7 March 2016 16:32:30 UTC+1, Thomas Broyer wrote: >>> >>> >>> >>> 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.
