I recently updated the ADT eclipse plugin from 22.x to 23.0.3. Being aware that there is a bug that blocks a clean update, i downloaded ADT from scratch, so to make the suggested workaround.
Only with the ADT bundle, there is no support for native development (NDK), which I need for my project, and so I downloaded the NDK suport using the classic install new software...
No problems with the installation at all, I restarted eclipse to find that the indexer, working fine until then, gets blocked at some point (the % reached is irrelevant, since it changes everytime I try), and I have to restart eclipse, since it does not respond while using 93% of CPU.
Do you know if there is anything wrong with the newest adt package? (the actual version is 23.0.3.1327240). If so, is there any workaround to enable native support without getting this problem?
Related
To upgrade to a new version, the eclipse FAQ suggests to add a new repository and then install available updates. Upgrading to Neon, the corresponding repository is http://download.eclipse.org/releases/neon/.
On this page, it says:
NOTE: Due to structural changes you cannot update from a Mars (or prior) all-in-one package to a Neon version. If interested in the technical details, see bug 332989 and bug 490515.
I still tried to above procedure, but no updates were found. What is the best way to upgrade from Mars to Neon? A complete new installation? How do I preserve my settings?
The note on the repository page is right. Thanks to your report, I edited the FAQ to make it clear that upgrading packages from Mars to Neon is not supported.
Instead you need to to a fresh install for Neon (or later).
I tried to upgrade in the recommended way, by adding the repository links and doing an update, but then I got a lot of conflict messages. I foolishly tried to remove the conflicting software components, until it told me that Eclipse itself was the conflict! I posted my problem to the Eclipse Forums, and was told by a regular with tens of thousands of posts that Neon was so different that I should not even try to upgrade, just create a new installation. When I tried to do that however, I got lots of warnings "That the artifact download is progressing very slowly from ..."
It is not possible to upgrade from Mars (or earlier versions), so a new install is needed.
This can be in parallel with the old install. From the FAQ:
Fresh install
If you prefer not performing an update (for example
because some 3rd-party content isn't ready for the current release of
Eclipse IDE so the update reports conflicts), you can still download a
fresh install of the Eclipse IDE and install it in another location on
your filesystem, and use it together with the previous version.
To do so, download a new build from the Eclipse download Web site
(https://www.eclipse.org/downloads/eclipse-packages/) and run the
installer or unzip the archive in a new directory. We strongly
recommend against installing/unzipping over your existing version of
Eclipse IDE as it may corrupt your installation.
When you start a new version of Eclipse IDE, you can use the same
existing workspace folder that you were using with older version. The
workspace will be migrated to newer version and Eclipse IDE will to
reuse all configuration. The workspace is forward compatible
So I am trying to run a google web application through eclipse, but when I run it gives me an error to please check for newest SDK version, which is 1.9.1. And sure enough Im working with 1.9.0, but I cant find any updates for GAE and it says all components are installed under help->install new software.
Ive tried downloading .zip file of 1.9.1 and extracting it to my eclipse\dropins dir but that doesnt do anything either. What do I do after Ive extracted it in to my dropins dir? And why cant I find the new version using eclipse own installation tool? Should I really be getting this error?
Try Eclipse Help -> Check for Updates instead. Sometimes the SDK detects a new version before Eclipse does, and everything synchronizes within a day or so. The SDK message is informational, not an error, so you can safely ignore it in the meantime.
In addition to what Martin suggested, you can download the SDK separately and unzip that in any separate folder. Then from your Eclipse Preferences, go to Google, App Engine SDK and select that particular version folder.
FYI - I prefer keeping the SDK versions separate from Eclipse. That way, I have the entire list of SDKs available in another folder structure and can use it across Eclipse versions too.
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.
In the past I've always downloaded the new version, and then manually reinstalled all of the plugins I use - but this is tedious in the extreme.
Is there a way to upgrade Eclipse "in-place"? How do I do this exactly?
The approach below worked for me, and seems to be the easiest. It's from this eclipse FAQ and slightly modified for clarity:
For upgrading from Eclipse 3.5+ to 3.6+
Help -> Install New Software
Enter the release update site url eg. 'http://download.eclipse.org/releases/indigo' <- if upgrading from 3.5 or 3.6 (Helios) to 3.7 (Indigo)
Click Add
Click Cancel
Help -> Check for Updates
Note: The original URL has changed. (I've left the original link for posterity)
following the NEW FAQ instructions
Also you may have to remove any incompatible updates plugins before proceeding.
(For Example: JBoss Tools has different versions for Helios and Indigo that are incompatible)
Update: I didn't try this when upgrading from 3.x to 4.x (Juno). I just set up a whole new workspace. I think I read somewhere that doing that is the safest approach to upgrading major versions.
As of 3.7 (Indigo), you may export/import install configurations via the
File > Import/Export > Install menu.
This allows you to install a new release of Eclipse, point it at your
existing workspace, and install your plugins from an older installed
copy.
If you always download all plugins manually and then deploy it by copying to dropins folder, then while migrating to newer version, just need to copy that folder to the new eclipse.
And even not all plugins will support newer version of Eclipse so I guess there is no really easy way available to do the migration.
The answer is, there is none. It's pointless to speculate here as to why the Eclipse community chooses not to make one. They haven't.
I am struggling with this!
While trying to install some features - eclipse keeps complaining about some dependency not met and about old version of some dependencies. The messages are rather not straigtforward.
Is there a way to clean the eclipse installation of the unused plugins? Does eclipse tell you on its own as to which features/plugins have not been used (for a while)?
What would be the definition of an unused plugin? All plugins that Eclipse update manager is referencing are currently in use because they were installed directly or are referenced by plugins that were installed directly.
I am not aware of anything that would actively track which features you are utilizing while using Eclipse and then report on unneeded plugins.
The error that you are running into typically happens because plugin A that you have depends on plugin X v1 and you are trying to install plugin B that requires X v2. Since both v1 and v2 of X cannot be simultaneously installed, installation of B aborts.
Here are the two most common causes of users finding themselves in this situation:
You haven't run "search for updates" recently, so many of your plugins are on older service levels. The plugin you are installing, however, requires a newer service level of a particular plugin. Resolve by updating your installation prior to trying to install the new plugin.
The plugin you are trying to install was not designed to be compatible with the major version of Eclipse that you are running. For instance, you might be running Eclipse "Galileo" 3.5 platform while the plugin you are trying to install was designed to work with Eclipse "Helios" 3.6 platform. You cannot use the update manager to move between major releases. Pay attention to what yearly release the plugin advertises support for. If it needs a newer version and you are willing to upgrade, you will need to download a new package.
Outside of that, post a new question with specific failure message you are getting along with details about your current installation and what you are trying to install. Someone here ought to be able to translate the installation failure into resolution options for you.