[appengine-java] Re: trouble with SDK 1.2.6

2009-11-12 Thread a.maza
same here, when I try to have my junit tests in the same project. anyone got a solution? On 28 Okt., 18:22, Vince Bonfanti vbonfa...@gmail.com wrote: No, that didn't help. Again, just to make sure I'm being clear:  - The only reason appengine-api-stubs.jar and appengine-local-runtime.jar are

[appengine-java] Re: trouble with SDK 1.2.6

2009-10-23 Thread Vince Bonfanti
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

[appengine-java] Re: trouble with SDK 1.2.6

2009-10-23 Thread Vince Bonfanti
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,

[appengine-java] Re: trouble with SDK 1.2.6

2009-10-23 Thread hildenl
Eplicitly add appengine-java-sdk-1.2.6\lib\agent\appengine-agent.jar to your java build path. On Oct 23, 11:06 am, Vince Bonfanti vbonfa...@gmail.com wrote: I'm having no luck with SDK 1.2.6 within Eclipse 3.5.1 (Windows). Yes, I've added the -javaagent VM argument to my debug configuration.