This will be a quick post. Did you update the ADT plugin to v17? Did you find that there are problems with libraries?
The solution (for some of those problems) is:
- If your jar libraries are in a lib folder, rename it to libs.
- Remove all your jar libraries from the Build Path of your project. Don’t need to add them again to the Build Path.
- In your libs folder, you should have just the jar libraries that your project is using. You can’t have different versions of a single library. This is because if you’ve noticed, Eclipse creates now a reference in the Build Path called “Android Dependecies” and he puts there all the jar files that are in your libs folder.
- Follow steps 1, 2 and 3 for each Android Library Project that your project is using.
- Make a project clean.
Hope it helps anybody! 😀
I found some help here: http://android.foxykeep.com/dev/how-to-fix-the-classdefnotfounderror-with-adt-17
UPDATE: You can find official ¡nfo on Android Dependecies at this link: http://tools.android.com/recent/dealingwithdependenciesinandroidprojects
Today I’ll write about how to have 2 fragments in one Activity, one of them containing a ListView (for example), and the other one containing a MapView, and all of this with a supercool ActionBarSherlock! The perfect combo!
It’s quite simple: if you want to use fragments with a MapView, you’re not allowed to do it in an easy way.
There’s no MapFragment that can be held by a FragmentActivity or a MapFragmentActivity that can hold both a MapView and some fragments #fail. So, what’s the solution?
First of all, who am I?
Hey there! I’m Xavi Rigau, a 21 year old Spanish student (I’ll finish my IT degree this summer) who loves Android Development. I started programming for Android as a hobby in the summer of 2009, but when I started university again in October I left it for a while.
Then I started my internship in a company called Tempos 21 in October, 1st 2010. It’s a consultant specialized in mobility. First day I did some boring stuff because I was supposed to be in the Testing department. The problem was that there was only one Android developer (which name is Paulo) at that time and when I said that I had programmed a little on Android they thought it should be better if I could help Paulo a little. Since then I’ve been working there as an Android developer, so I’ve been into this 1 year and a half now.
I’ll be posting info about Android development soon!