I've identified a bug in the precompilation process (well, another symptom of a problem we were already working on fixing).
As a workaround, if you can stop providing play-gae.jar in both WEB-INF/lib and WEB-INF/modules/gae/lib this issue should go away. Those two files just need to not have identical contents (they can still be named the same and contain effectively the same class files, if you'd like). On Thu, Mar 11, 2010 at 7:47 AM, guillaume <[email protected]> wrote: > Hi, > > I manage the Google App Engine module for the Play! java web framework > (http://www.playframework.org). While generated applications run > correctly on the local and production runtimes, the precompilation > process always fail. > > It seems that any war generated by play cannot be precompiled (So for > example this app: http://play-lists.appspot.com). > > It's true that we are doing a lot of very dirty hacks in play > framework... > But any chance to have a hint on why the precompilation process fail? > This way I could try to find a fix. > > Thank you. > > Guillaume. > > -- > 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.
