It looks like the Eclipse debug configuration automatically picks up the complete build path for the project as its classpath. Manually editing the debug configuration to remove appengine-api-stubs.jar and appengine-local-runtime.jar from the classpath fixes the problem.
Vince On Fri, Oct 23, 2009 at 3:01 PM, Vince Bonfanti <[email protected]> wrote: > > I just figured out the problem. I had added appengine-api-stubs.jar > and appengine-local-runtime.jar to my project build path to support > junit testing. Upgrading to the 1.2.6 versions only changed the error > message, but removing them from the build path solved the problem. Now > I just have to figure out how to configure things properly to support > junit testing... > > Thanks. > > Vince > > 2009/10/23 Miguel Méndez <[email protected]>: >> I'm going to check and see if I can reproduce this using your project. >> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
