> :: shrug :: > > It works for many other developers, including hundreds of students of > mine. Since the non-Eclipse portion is pretty bulletproof, and since I > don't use Eclipse, my guess is that your problems stem from something > Eclipse-related, perhaps in the way you are putting it in your build > path.
I don't doubt that it works actually and I do think it has to do with either how I configured the plug in or some other issues with Eclipse - the build path etc I know that pretty well so I don't think that's the problem. I will post a solution once I find it to help anyone else who may have the same issue. > > > The libs dir is either in the src dir or the top level > > dir. > > The libs/ dir is supposed to be in the root of the project dir. Now, I > have heard that you can have it located elsewhere when you are > building with Eclipse, but I have not tried that. I tried both - I will keep it in the root dir to be on the safe side and eliminate at least that unknown. > > Once I move > > it in the assets dir I can see it being wrapped inside the apk. > > I suspect having it there will be useless. Ack. On a related note - I think the http commons (apache) is part of the Android platform but in the general scheme of things is there a repository somewhere that stores 3rd party jars compiled for Android (similar to ibm's wsdl, bouncycastle etc.)? Thanks again -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en