Develop Reference

Create New Android Project In Eclipse Fails

When I want to create a new project in eclipse it gives me this error every time.
I have installed ADT using Eclipse->Help->Install New Software.
I have installed sdk and jdk and.
What is problem? it really gets me sick. I will throw my computer away.

Try the nightly build of Andmore (unofficial Android dev tools, you may be using it, but not nightly perhaps). I can't tell you if that works or not, but they did update the support libraries. Add this to your update sites: http://download.eclipse.org/andmore/nightly. Also make sure to go onto your Problems tab and delete all (not sure if Andmore clears them) then clean projects in menu.

U have to add appcompat library in your project. If u want to use appcompat.

How to fix corrupted Eclipse Indigo JEE?

I installed following plugins in eclipse indigo in following order to start spring development
Spring Tools Suite
M2E (Maven)
after these two installations, it was giving error
jira connector not installed, so I installed the following plugin.
Atlassian Jira Connector
After installing Jira Connector, Eclipse Started showing the following error :
Uninstalled Jira Connector. Still Showing these Problems.
Any help would be appreciated.

Eclipse has major structural problems with uninstalls, which aren't really fixed even the latest luna. But don't worry, there are a lot of workarounds.
What you can do now and in similar situations:
1.
If you can even uninstall something, you won't get back its previous state before the install.
Because of it I use Eclipse normally with a trick: I store my main Eclipse install directory in a git repository, and so I can always switch back with a single command. But it is only a trick.
2.
There is a big chance, that only your workspace directory is damaged, and not your Eclipse. In this case you can solve this problem by reinitializing your workspace: make a backup, delete everything, recreate your workspace directory and finally import again your projects.
(For similar reasons it is also an useful trick to save your workspace metadata in a git repository as well.)
3.
In Eclipse, the menu items are created by modules. If an eclipse module is installed, it creates the changes in its internal configurations which create the menu items.
After a restart, Eclipse tries to restore your gui, and thus re-open its panels. But if a module uninstall is also happened, then its panels aren't restorable, resulting exactly your problem.
So, simply close the bad panels and try to reopen them. Sometimes it also works.
In short: recreate your workspace, it will probably help. And next time, use Eclipse with some good and frequent backup (I suggest git).

Update ADT from 21.0 to 21.1

i downloaded APIs 15,16 and 17. After the download is finished, I closed eclipse but when i open it again it gives me a message box saying I need to update my ADT from 21.0.0 into 21.1 or higher, (and my current project suddenly didnt work, and full of red lines). There is a "Check for Updates" button. But after clicking it, it says there was no update found. I asked Google and found out that there is already ADT 21.1 released. I am wondering if I should just download the latest ADT bundle, but also looking for a quicker solution. I said “quicker” because my internet connection is a bit slow. :( It will take me a whole day to finish the download. :( And also after i downloaded the API, my graphical layouts do not show any more. There is a message saying "Eclipse is loading the SDK. Home.xml will refresh automatically once the process is finished." I waited for eternity, but nothing shows up. Im pretty messed up here. My project does not work anymore, although it worked well before i downloaded the APIs. Can anyone help me?. Thanks.

Go to eclipse > help > Check for updates.
It should list the latest update of adt. If it doesn't work, try this :
go to eclipse > help > Install new software
Click on add
add this url : https://dl-ssl.google.com/android/eclipse/
It will list the updates available- which should ideally be adt 21.1.0 (latest)
install the latest adt and everything should be fine.

The same thing happened to me, here's what I did-
Apparently, the SDK updated to version 21.1, but ADT, still at 21.0. 21.1 is currently a preview release (so I'm not sure how we accidentally updated the sdk...), so you have to manually add the update source. There's a nice guide (http://tools.android.com/preview-channel), but here's what you need:
Start Eclipse, then select Help > Install New Software.
Click the "Add" button, in the top-right corner.
In the Add Repository dialog that appears, enter "ADT Previews" for the Name and the following URL for the Location:
https://dl-ssl.google.com/android/eclipse-preview/
Click OK.
If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
This worked for me, although I would rather have just downgraded the sdk.
Hope I helped!

go to window -> SDK manager and then install Android SDK Tools to 21.1 and then check for updates again.
I used to get error " update cannot be installed " for that run eclipse in Admin permission.

same with your problem !!!
btw, Thanks for the info ! I tried it after read this and wohooow It worked ! thx
go to eclipse > help > Install new software
click on add
add this url : https://dl-ssl.google.com/android/eclipse/

Android Eclipse Classpath - want to add classpath container path but eclipse won't let me

I'm using Eclipse to learn to develop Android applications in Java. I haven't used Eclipse before.
The project I'm trying to use (supplied by OReilly as part of 'Android Application Development') is MJAndroid. When attempting to run the project, the Run fails, and the Problems tab mentions com.java.Object can't be found, and Eclipse asks me to check the build path. Clicking
Properties -> Java Build Path -> Libraries, the message 'Unable to get system library for the project' is displayed.
On a working project, Properties -> Java Build Path -> Libraries has an entry for Android 1.1, which if I click Edit, has the classpath container path of com.android.ide.eclipse.adt.ANDROID_FRAMEWORK.
It seems a simple matter of adding the correct container path to my non-working project. However Eclipse seems determined to make this as difficult as possible. No matter what I chose to add - jars, externals jars, variables, libraries, class folders, external class folders, nothing seems to take the form of 'com.android.ide.eclipse.adt.ANDROID_FRAMEWORK' that the 'Android 1.1' entry on the working app has.
How can I add this namespace to my project so it resembles the working one?
I'm quite sure it's a problem with Eclipse's somewhat odd user interface. Frankly there' nothing I'd prefer more than a file to modify and set such information - my background is in Python, and the whole eclipse environment seems an unnecessary burden.

I had faced the same issue when I imported a sample code downloaded from the internet. I am using android sdk 1.5 with 0.9 ADT plugins. Here is a simpler way to fix the andoid library reference issues
Right click on the project which has
issues and select properties
Select the appropriate Android build
(1.1, 1.5 or 1.5 with google api) and
say ok
Again right click on the project and
select "Android Tools > Fix Project
Properties"
Fix the imports once (if required)
Refresh the project and you should be
ready to go without any manual
editing

I faced this same problem after importing a project through GIT. The problem was that I didn't have the same target android platform installed, and the build path somehow got corrupted.
The first obvious thing i did was changing the target sdk in the project.properties, but even after cleaning up the project and Android Tools > Fix Project Properties, it didn't help and I was still getting the build error.
My solution after wasting close to 1 hour trying to figure this out?
RESTART ECLIPSE
Everything worked fine after that. Eclipse is pretty fickle. Only through years of experience you'll then understand her well. :)

Had the same problem and it turns out the Android SDK Location was not set which was a really simple fix. Go to Window->Preferences, click on 'Android' on the left hand menu, fill in the location of the Android SDK (e.g. C:\Program Files\Android\android-sdk) and click OK. Everything worked fine for me after that.
Found the answer in this set up guide: http://developer.motorola.com/docstools/library/Installing-Android-Dev-Environment/

Sometimes Eclipse can get a bit funny (technical term) with classpath container resolution.
You have a working project in your workspace, so you can rule out plugin installation issues. You could try opening the .classpath file (hidden by default, select the triangle in the top-right of the Package Explorer view, select Filters... and uncheck .* resources) and manually adding the container declaration.
`<classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>`
You may then have to close the project and open it again (right-click->Close Project) before Eclipse recognises the change.
You may also find that there is an Android builder and/or nature. If you compare the .project files for the working and non-working versions you may see entries for Android builders/natures. Copying the relevant entries may resolve the issue.

sometimes, eclipse can help you.
In Android projects, click right button on the project-> Android Tools -> Fix Project Properties.
It's usefull in class path errors!!
Luck!

I would verify you have the correct version of Java installed as well as the Android SDK. I would recommend installing/reinstalling the ADT plugin in your eclipse, makes it alot easier to create the android project.
http://developer.android.com/sdk/1.5_r2/installing.html

Also. I guess the path of the Android SDK must be setup correctly. This happened when I was overloaded with projects and I decided to create a new workspace copying some existing stuff into it.
Seems that the new workspace requires you to setup these details too once again
Is that setup properly?

How to uninstall plugins in Eclipse 3.4.X or higher

The GUI for managing plugins in Eclipse got a bit of an overhaul in version 3.4.0.
This GUI is accessed via the "Software Updates..." option in the Help menu.
The option to remove the selected Mylyn plugin is greyed out. In fact, this is true of virtually every installed plugin. I know that the Mylyn plugins are optional, so why amn't I provided with an option to remove them?

The following text is quoted from the Eclipse help docs:
The Uninstall wizard allows you to review and uninstall items in your configuration. This wizard is shown when you select items and press Uninstall... from the Installed Software page. To uninstall software from your system:
Click Help > About and then click Installation Details... to open a dialog showing pages that provide more detail about your installation.
Click the Installed Software tab to see a list of the software items that you have installed into your system.
Select the items that you wish to uninstall.
Click Uninstall...
The Uninstall Details page will show you a list of the items that will be uninstalled. Expanding each item will show what additional items (if any) will be uninstalled as a result of your choice.
If you change your mind about which items should be uninstalled, you may click Back to see a checkmark list of the items you selected before. You may check and uncheck different items in the list, and click Next when you are ready to continue.
Click Finish to start the uninstall.
Once all of the software is uninstalled successfully, you will be prompted to restart for the Workbench. Click Yes when asked to exit and restart the Workbench for the changes to take effect.

And just to update it for Helios - Eclipse 3.6
Help->Install New Software at the bottom of dialog there is link What is already installed once you click on that you will get list of installed plugins and Uninstal... button

eclipse 3.5(Galieo)
Help>> Install New Software >> Already Installed Plugins >> select Plugins >> Uninstall works charm.

There are distributions of Eclipse that come packaged with certain plugins that can't be mix-and-matched. That is the case with Mylyn, that went from a student's thesis project to an integral part of Eclipse. If you want to actually get rid of Mylyn, you may want to install Eclipse classic instead of the distribution you have, and then install the stuff you need.
The standard Eclipse distributions come with Myln.
BTW, Eclipser 3.5 completely changes all these screens :(

If you are using Windows, make sure you are running Eclipse as administrator. Without administrator privileges, some options may be grayed-out in "Installed Software".

In eclipse Helios (version 3.6), to uninstall a plugin:
Go to Help->Install New Software...
Click on "What is already installed?" link at the bottom right side of the dialog
In the Installed Software tab choose the software you want to uninstall
Click on the "Uninstall..." button at the bottom
Click 'Finish' on the Uninstall Details dialog
Observe the 'Uninstalling Software %' status at the bottom status bar of eclipse
Click 'Restart Now' when prompted to do so.
Eclipse restarts. Choose the workspace. Now when you go again to the Installed Software window , you do not find the uninstalled software.

In Eclipse 3.6 Helios, the interface has changed again. Go to "About Eclipse", and then click the "Installation Details" button in the about box.

While Help → About Eclipse IDE [or wherever it was in the past or will be in the future] → Installation Details → Installed Software → Uninstall... is the official and preferred way there are features/plugins the latter button of which is disabled.
Remember also that there aren't only plugins but features too. In my case I wanted to remove Mylyn and Wild Web Developer from a rather fresh Eclipse IDE for Enterprise Java and Web Developers package. I did the following.
But first a:
DISCLAIMER
Enter ECLIPSE_HOME at your own risk. Mistakes like typos might be in the following, too. I take no responsibility for whatsoever.
Created the directories features.DISABLED and plugins.DISABLED in Eclipse's home dir.
Moved *mylyn* from ECLIPSE_HOME/features to ECLIPSE_HOME/features.DISABLED
Moved *wildwebdeveloper* from ECLIPSE_HOME/features to ECLIPSE_HOME/features.DISABLED
Moved *mylyn* from ECLIPSE_HOME/plugins to ECLIPSE_HOME/plugins.DISABLED
Moved *wildwebdeveloper* from ECLIPSE_HOME/plugins to ECLIPSE_HOME/plugins.DISABLED
After starting Eclipse there were about a dozen "not found" errors in Eclipse's Error Log view. If you double-click on each of them you can see which dependency plugin JAR(s) haven't been found.
Set the Error Log view's filter to just display errors and warnings.
Moved the dependency plugin *.jars mentioned in the errors from ECLIPSE_HOME/plugins.DISABLED back to ECLIPSE_HOME/plugins one by one (with Eclipse restart after each) until no "not found" error appeared in the view any longer. It were nine *mylyn*.jars in the end.:
*.mylyn.commons.core_*
*.mylyn.commons.net_*
*.mylyn.commons.notifications.core_*
*.mylyn.commons.notifications.ui_*
*.mylyn.commons.screenshots.ui_*
*.mylyn.commons.ui_*
*.mylyn.commons.workbench_*
*.mylyn.commons.wikitext.markdown_*
*.mylyn.commons.wikitext.*
Note that this applies to a rather fresh Eclipse 2021-03 (4.19.0) installation. It might be different from one – even patch – version to the other.
Furthermore:
Keep Eclipse's Error Log view open for a while. The underlying OSGi activates bundles (plugins) on the fly if they are referenced from an other bundle (plugin) for the first time. And if one isn't there then...
Check the Error Log view especially after installing new features/plugins. They might rely on plugins/JARs you moved to .DISABLED. If that's the case move the according JAR(s) back to ECLIPSE_HOME/plugins and/or ECLIPSE_HOME/features.
If something doesn't work as it did in the past once in the future remember what you did and ... → Error Log view.

I'm running (a relatively fresh copy of) 3.4.1. I was able to select the same plug-in shown in your screen shot (Mylyn Bridge: Java Development) to get an enabled "Uninstall..." button. I'd suggest getting the latest updates and trying again.

It sure looks like there's no way to do this.
I just had exactly this problem with a fresh download of the Eclipse Java IDE (Ganymede SR2). I didn't want Mylyn, but I didn't want "Eclipse Classic", either, because the download was twice the size, I presume because it includes source.
The apparent solution was to update everything and restart Eclipse, after which the "Uninstall..." button became enabled for the Mylyn plugins. Unfortunately, this only uninstalled the most recent, updated version (3.0.11 IIRC), reverting to the un-uninstallable 3.0.5.

I just don't know what the hell these Eclipse developers are thinking! Removing plug-ins from Eclipse became a pain in the ass since Helios!
I hear you pal... I just went through the whole day trying to figure out as no one seems to give an straight answer like "do this, that, done."
Man I'd rather be programming instead....
Found, in the middle of my evening that it is possible to uninstall pretty much everything. The issue is that the damn thing is hidden in the "HELP->ABOUT". Who would guess after going over and over through the "Help->Install New Software" or "Help->Check for updates" and never finding anything like "remove" or "reinstall" or "force reinstall".
Seriouly, I'd rather go back to 1990 when we had Microsoft, Borland and Watcom.. you picked your platform and you'd be with 1/3 of the world of developers with you.. ok, perhaps Watcom didn't hit that mark but you get the point.
So... to uninstall any plugin from Eclipse Helios (Service Release 1) or Springsource 3.5.2 (or 3.6.1 I 'm using), do this:
close all your projects (just to be on the safe side);
Hit menu "HELP-->ABOUT" (yeah.. help, about);
Hit "Installation Details" button and you get the list with all plugins;
Click on the one you want to remove; hit uninstall;
If want to remove more than one, just apply the change without restart;
Goto to 4) as needed
Finally, restart Eclipse and reinstall what you need !
It was hard to find, but it worked very well for me.