I\'ve been working with Eclipse 4.2 (Juno release 20120920-0800) on OS X 10.8.2 for a few weeks now, building apps for Android 3.0 and above. I have a quad core i7 MacBook P
There are various reasons for this problem, and each have a different solution. For a Linux environment, I made a alias to take care of most of these as they happened overtime. To have all of those in one place, you could try this:
Add the following in your ~/.bash_aliases
file.
alias eclipse='rm -rf ~/.android/ddms.cfg;rm -rf ~/workspace/MyApps/.metadata/.plugins/org.eclipse.core.resources/.projects/*;mv ~/workspace/MyApps/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi ~/workspace/MyApps/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi.bkp;rm -rf ~/.android/cache/;cd ~/Desktop/adt-bundle-linux-x86_64-20140702/eclipse;nohup ./eclipse & cd -;'
Refresh source using source ~/.bash_aliases
Note:
~/workspace/MyApps
is my workspace, you'll have to configure your's accordingly.
~/Desktop/adt-bundle-linux-x86_64-20140702/eclipse
is the location of my eclipse executable,and you'll have to configure your's accordingly
I made this batch file to fullfill the task explained by slhck's answer for Windows systems:
@echo off
set ECLIPSEFOLDER=%CD%
cd /D %USERPROFILE%/.android
rd /s /q cache
del ddms.cfg /f
cd /D %ECLIPSEFOLDER%
eclipse -clean -refresh
exit
I explained such approach in this post on my blog.
just right click on eclipse and run it as a administrator i was also having the same problem after this it was working fine actully sometimes the windows do not give the permission to access to sdk in normal user so you have to give admin permissions in order to work android sdk or content loader
this approach:
shut down eclipse then go to YourWorkSpace\.metadata\.plugins\org.eclipse.e4.workbench and remove "workbench.xmi", now restart eclipse.
My solution:
Install all the Docs in the sdk manager.
All the above solutions didn't work for me.
In eclipse Under Problems Tab check errors- You might see the unable to delete file and project path name.
Now Go to your workspace directory - Check project.properties for all the project stated under problems tab and check
target=android-21
The target value is valid and exists in your android-sdk/platforms/ folder
In my case target=Google,Google-Api-16 was causing the issue. Replace that and it solved.