Okay, I figured it out. Basically there's 2 steps. 1. In Eclipse under the project Properties -> Android -> Android 2.0. This is suppose to swap the Android Library files under Java Build Path. I had originally deleted the 1.6 Library, and manually added the android.jar in the Android 2.0 platform and that is incorrect. The system has to switch the library packages. 2. If still having some problems, right click on the projects folder - > Android Tools -> Fix Project Properties.
These 2 steps got my 2.0 to finally run. On Nov 11, 3:27 pm, Sam <samm...@gmail.com> wrote: > Hi, > > I just updated and ran into the issue. Can you please provide step by > step what you did to solve this? > > Sam > > On Nov 5, 4:03 am, vachudj <vach...@gmail.com> wrote: > > > Hi, > > I had the same problem. > > I solved it by removing 1.6libraryand appending 2.0library. > > The just changing the 2.0's android.jar file instead of 1.6libraryis > > not sufficient. > > The android.jar file must be represented in project as newlibrary. > > > Hopefully it helps... . > > > On Oct 30, 5:01 am, JP <joachim.pfeif...@gmail.com> wrote: > > > > OK fixed. > > > I've toyed around a little more and, in Eclipse, applied Android Tools> > > > Fix Project Properties. > > > > That created a single Google APIs [Android 2.0] entry in Libraries, as > > > opposed to the two individual entries android.jar and maps.jar > > > For future reference. Hope this helps someone else. > > > > On Oct 29, 7:51 pm, JP <joachim.pfeif...@gmail.com> wrote: > > > > > After getting comfy with the Android 2.0 environment and emulator (for > > > > the most part), I took the next step to bind <myapp> against the > > > > latest Android 2.0 jars: android.jar and maps.jar > > > > > The existing code (working in Android 1.6) did not need any changes to > > > > compile, but the app doesn't build due to a weird error message that > > > > prevents the build. See snippet below, drawn from the Eclipse > > > > Console. > > > > I have no aspirations to run up against anycorelibraryclasses, and > > > > I am not aware I do. In other words, I am not implementing > > > > SealedObject (or any othercoreclassthat I am aware of) that would > > > > run up against Dalvik. Not in the javax, java or any other namespace. > > > > Anybody got any pointers what's going on here? > > > > > <----- Snippet ----> > > > > > [2009-10-29 19:37:42 - <myapp>] > > > > trouble processing "javax/crypto/SealedObject.class": > > > > [2009-10-29 19:37:42 - <myapp>] > > > > Attempt to include acoreclass(java.* or javax.*) in something other > > > > than acorelibrary. It is likely that you have attempted to include > > > > in an application thecorelibrary(or a part thereof) from a desktop > > > > virtual machine. This will most assuredly not work. At a minimum, it > > > > jeopardizes the compatibility of your app with future versions of the > > > > platform. It is also often of questionable legality. > > > > > If you really intend to build acorelibrary-- which is only > > > > appropriate as part of creating a full virtual machine distribution, > > > > as opposed to compiling an application -- then use the > > > > "--core-library" option to suppress this error message. > > > > > If you go ahead and use "--core-library" but are in fact building an > > > > application, then be forewarned that your application will still fail > > > > to build or run, at some point. Please be prepared for angry customers > > > > who find, for example, that your application ceases to function once > > > > they upgrade their operating system. You will be to blame for this > > > > problem. > > > > > If you are legitimately using some code that happens to be in acore > > > > package, then the easiest safe alternative you have is to repackage > > > > that code. That is, move the classes in question into your own package > > > > namespace. This means that they will never be in conflict withcore > > > > system classes. If you find that you cannot do this, then that is an > > > > indication that the path you are on will ultimately lead to pain, > > > > suffering, grief, and lamentation. > > > > > [2009-10-29 19:37:42 - <myapp>]1 error; aborting > > > > [2009-10-29 19:37:42 - <myapp>]Conversion to Dalvik format failed with > > > > error 1 > > > > > <----------- Snippet ----------------> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
