Eclipse + cupcake + referenced projects in build path = VerifyError

by Inderjeet Singh » Tue, 28 Apr 2009 23:34:50 GMT

Sponsored Links
 I ran into the same problem this morning and was hating myself for
being a compulsive early adopter. :)
Also, the fact that you actually have to create a device before you
can launch anything.

Anyone else figured out what is going on?


On Tue, Apr 28, 2009 at 8:02 AM, Guillaume Perrot


Eclipse + cupcake + referenced projects in build path = VerifyError

by Raphael » Wed, 29 Apr 2009 01:17:52 GMT

 One thing I generally do for this case is to create regular Java
projects for the libraries, then remove the jre from the classpath and
put the android.jar instead.

That method however has a couple caveats, namely that a/ the
android.jar uses a full path (a pain if you have an SCM and different
setups) and b/ you need to update it each time you update the SDK
(which you probably don't do that often.)


On Tue, Apr 28, 2009 at 8:02 AM, Guillaume Perrot


Sponsored Links

Other Threads

1. How good to use intents with an application to communcate and modularise it

On Sat, Jan 31, 2009 at 8:12 PM, Raja Nagendra Kumar <

You missed the disadvantages, the main one being that you are then
responsible for keeping track of the full state of your application so that
it can be recreated when the user returns to it after its process has been
killing or changes the configuration it is running in by for example
rotating the screen.  This can actually become a significant amount of
effort to do well, since you need to limit as much as possible the up-front
work you need to do to get your UI re-created in whatever state it should be

I would strongly caution against trying to use models from J2ME to help
understand Android.  Pretty much no part of these aspects of the design were
influenced by J2ME.

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.


2. Specific Design significance of Attribute Name Spaces in AndroidManifest Files.

Attributes live in the global namespace by default; they do *not* inherit
the default namespace, unlike elements.

On Fri, Jan 30, 2009 at 11:14 AM, Raja Nagendra Kumar


3. Sending Intent to specific Activity

4. Math.Sin(90) doesn't return 1?

5. sensors HAL limitation

6. Does OpenCore support MP3 within MP4 container?

7. Unlocked Phone Question