Solution to update Android SDK independently without using Eclipse

12 Comments


Recently when I tried to update Android SDK to latest version i.e 2.2, API 8, revision 2 from eclipse, I got a warning on the lines below

Failed to rename directory

-= Warning ! =-

A folder failed to be renamed or moved. On Windows this typically means that a program is using that folder (for example Windows Explorer.) Please close all running programs that may be locking the directory.

Many people have reported this error and though there are various solutions (like renaming the tools folder under <Android_Installation_Path>\android-sdk-windows\tools and update from that folder etc), there is no single solution that fixed this bug.

Ther bug is also reported in the code.google.com

http://code.google.com/p/android/issues/detail?id=4410#makechanges

The core issue is indeed somebody else locked the tools folder. So I tried the following solution and it worked like charm

  • Close Eclipse and close all instances of windows explorer in which the <Android_Installation_Path>\android-sdk-windows\tools folder was opened
  • Now run the AVD Manager independently as follows
  • Open a command prompt.
  • Go to the directory where android sdk is installed at, and then its tools subdirectory.
  • Run Android.bat.
  • At this point, update just as you would if you were running the AVD Manager from within Eclipse (make sure the proxy settings are mentioned if you are behind the proxy).

You should be able to update the Android SDK now.

The project cannot be built until build path errors are resolved – Error in Eclipse IDE

20 Comments


Following content is referenced from

http://www.scottdstrader.com/blog/ether_archives/000921.html

Opening a workspace with several projects, I was presented with the following error for two of the projects:
To resolve this error in eclipse do the following steps.

The resolution was to force a resave of the selected projects (and their .classpath files):

Open the project properties
Select Java Build Path > Libraries
Add a new, arbitrary library (to be deleted later) > OK
Wait for the workspace to refresh (or force a refresh of the project)
The error(s) will go away
Remove the dummy library
The only other references I could find were to make minor alterations of contents of the .classpath file.

Setting up J2ME development environment

Leave a comment


Setting up J2ME environment

1) Install Eclipse Pulsar for Mobile Java Developers from

http://www.eclipse.org/downloads/

2) After installation, please use help section of the eclipse to find out how to create MIDlet suite because the information given there is well structured and easy to follow.

Happy J2ME coding !!!