Hi Keith, Regarding multiple/single project(s) and unit tests:
I currently have all tests included within the same single project. The disadvantage of this however seems to me that all tests classes (including extra jars only needed for testing (like appengine- testing.jar)) will also be deployed to GAE. Furthermore, my source base is growing into a size that it might be better to split off things into separate projects. I am not that familiar (anymore) with developing large projects under eclipse, so I am not sure what a proper way would be to setup multiple projects in general. But I can't imagine all GAE & GWT undertakings are done with a single project. Any suggestions? thanks in advance, Rutger On Mar 22, 9:24 pm, Keith Platfoot <[email protected]> wrote: > Hi Vlad, > > You should be able to develop and debug App Engine applications in Eclipse > for Java EE in much the same way you would a GWT application, although there > are a few key differences. I believe the main difference is that with App > Engine, you will need to use its included Development Server > (http://code.google.com/appengine/docs/java/tools/devserver.html) rather than > your own app server (Tomcat, Jetty, Glassfish, etc.). The Development > Server simulates the runtime environment of Google App Engine, and is > necessary for testing datastore, login, etc. > > Regarding multiple projects: we generally recommend using a single project > if possible to keep things simpler. Also, the plugin may make it difficult > to split across multiple projects, if you run/debug directly from your > source WAR directory (project properties > Google > Web Application > > Launch and deploy from this directory). In this scenario, the plugin > automatically sets the project's build output path to <WAR>/WEB-INF/classes, > so you'll probably run into some issues with multiple projects, since they > each need to contribute class files and/or jars into that same WAR > directory. However, if you use Eclipse for Java EE and run GWT with > -noserver, multiple projects *should* work, since WTP will take care of > populating WEB-INF/classes and WEB-INF/lib automatically. > > Keith > > , although with Eclipse for Java EE, you may be able to get away > > On Wed, Mar 17, 2010 at 4:55 PM, Vlad Skarzhevskyy > <[email protected]>wrote: > > > Thanks Google for hard work! > > > In your FAQ you made a big efforts to support Dynamic Web projects in > > Eclipse for Java EE for GWT applications. Does the same apply for App > > Engine projects? > > > What is the recommended way to make complex GWT and App Engine > > applications? > > In template projects created by Plugin you see all in one project. > > Client and server are all together with one classpath. What would be > > the real world scenario with Client projects(modules) and server > > project(modules) all in separate Eclipse projects? > > > Regards, > > Vlad > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine-java%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
