Hi,
maybe I am the only one, but it at least seems that Java 1.8.1 devmode now features a hot redeploy mode for all contents of the classes (target) by default. In former times we had to touch appengine-web.xml - now the internal jetty picks up changes immediately. This is good news in principle. The problem, however, is that the devmode restarts after something gets written to my target dir. This is again is okay in principle - but breaks of course as the appengine test db is stored and generated by default inside my target dir: [INFO] Storage: blabla-1.0-SNAPSHOT/WEB-INF/appengine-generated/local_db.bin [INFO] Jun 13, 2013 12:05:30 PM com.google.appengine.api.datastore.dev.LocalDatastoreService load [INFO] INFO: The backing store, blabla-1.0-SNAPSHOT/WEB-INF/appengine-generated/local_db.bin, does not exist. It will be created. [INFO] Jun 13, 2013 12:05:31 PM com.google.appengine.tools.development.JettyContainerService$2 filesChanged [INFO] INFO: A file has changed, reloading the web application. This essentially makes developing with 1.8.1 impossible with the default configuration of the maven plugin. I am wondering if I missed something in the configuration or if this is just broken? Thanks, Raphael -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
