8

I'm working on a team project. I included a .jar file in Build Path and committed to SVN. When I updated code in my working directory, a new folder appears in Eclipse called "Android Dependencies". If I let it be there, my program runs; If I remove it, my program reports a ClassNotFoundException.

Now how to fix this ClassNotFoundException?

tshepang
  • 12,111
  • 21
  • 91
  • 136
emeraldhieu
  • 9,380
  • 19
  • 81
  • 139

4 Answers4

42

For the people whose heart dropped when they read the comment that deleting the Android Dependencies virtual folder will destroy your project, there is an easy fix.

  1. Right click on the destroyed project
  2. Select "Android Tools > Fix Project Properties" in the dropdown

I hosed my project dependencies when trying to set up my git repo, and this is fixed it.

kianatennyson
  • 511
  • 5
  • 5
7

Android Dependencies is a virtual folder where Eclipse shows what JAR files the project depends on. It's not a physical folder; you won't find it on your hard disk. And the folder is not checked in into Subversion.

Do not delete that folder. You will destroy your project.

To fix it, just revert to an older Subversion revision and check it in again.

Codo
  • 75,595
  • 17
  • 168
  • 206
  • Why don't I see it in some projects, sometimes I see it? Can you give me a reference link about it? I googled "Android Dependencies" but no site tell what it really is. – emeraldhieu May 28 '12 at 05:58
  • Updating doesn't recover it, I must delete it from local and re-update. – emeraldhieu May 28 '12 at 06:01
  • 1
    The folder renamed and extended with revision 17 of the SDK (see [Dealing with dependencies in Android projects](http://tools.android.com/recent/dealingwithdependenciesinandroidprojects)). So it depends on the revision of the SDK. – Codo May 28 '12 at 06:03
  • 6
    In the current version, just restarting Eclipse will re-create the "folder". – Carsten May 31 '12 at 01:40
  • @Codo, Where does Eclipse store these "dependencies" information at? – Pacerier Nov 14 '14 at 04:41
2

I've had a similar problem after setting up a git repo with my project.

The problem was that the appcompat import lost its folder reference.

If the 'Fix Project Properties' mentioned doesn't work for you try this:

  1. Go to Project > Properties
  2. Go to the 'Android' tab
  3. Under 'Libraries', if there's a red 'X' next to the appcompat folder, remove it then hit 'add' and add it in again. The reference should show a green tick now.
  4. Save and clean the project if needs be
Darragh.McL
  • 125
  • 1
  • 10
1

If you also have marked project build target below API level 16 in the Android project properties, the error is going to come because prior to this level, there was no Android dependencies.

Abhinav Saxena
  • 1,990
  • 2
  • 24
  • 55