Just for the record, I also have appengine-api-stubs.jar and
appengine-local-runtime.jar for my tests, and making appengine-agent
the first entry in my classpath solved the problem.

On Oct 28, 6:22 pm, 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 in my project classpath is to be able
> to compile my junit tests. They're not needed for debugging my
> project. However...
>
>  - When creating a debug configuration, Eclipse automatically uses the
> project classpath by default, which causes the exceptions I showed
> earlier when trying to debug. Adding appengine-agent.jar to the top of
> the project and debug classpaths did not solve the problem.
>
>  - By manually editing my debug configuration to remove
> appengine-api-stubs.jar and appengine-local-runtime.jar from the debug
> classpath, everything works fine.
>
> At this point I'm happy.
>
> Vince
>
> On Fri, Oct 23, 2009 at 3:55 PM, Toby Reyelts <to...@google.com> wrote:
> > Vince,
>
> > You should be able to workaround the problem you're having with your unit
> > tests by adding $SDK/lib/agent/appengine-agent.jar to the very top of your
> > system classpath. Please let me know if that does not work for you.
>
> > On Fri, Oct 23, 2009 at 3:23 PM, Vince Bonfanti <vbonfa...@gmail.com> wrote:
>
> >> 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 <vbonfa...@gmail.com>
> >> 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 <mmen...@google.com>:
> >> >> 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 google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=.


Reply via email to