Hey all, running into the 'cannot satisfy dependency' for several different plugins, and rather tackle all those different plugins just wondering if there is a way to simply install an older version of ICU4j (com.ibm.icu) as an eclipse plugin (preferably via update site).
thanks!
ICU4J is delivered through the Orbit project. Check which build has the version you want at http://download.eclipse.org/tools/orbit/downloads/ then use http://download.eclipse.org/tools/orbit/downloads/drops/RELEASE/repository as update site. I believe that for the archived builds the update site will be http://archive.eclipse.org/tools/orbit/downloads/drops/RELEASE/repository.
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
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.
How do I determine the update site/source of an installed Eclipse plugin?
For example, in one of my development versions of Eclipse I have the plugin org.hamcrest.library. From Help - About Eclipse - Installation Details - Plug-ins I can determine that the provider is Eclipse.org, but is it possible to determine the feature or update site from where it came so I can install this in a separate version of Eclipse I have?
All third-party open source bundles that are used by Eclipse are managed by Orbit project. You can install them from Orbit Repository.
I'm trying to install an Eclipse plugin for Mylyn/Fogbugz, and I get the following error when I try either EclipseBugz or Foglyn:
Cannot find a solution satisfying the following requirements Match[requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.swt
I'm using Eclipse 3.4.1
what other update sites do you have enabled in your Eclipse installation?
I had similar problem when upgrading from older Mylyn, and found out that it helps to disable other updates sites. When installing new plugins, or even updating old ones, Eclipse has a tendency to contact all enabled update sites. I don't know what exactly it is trying to do, but it helped me to disable all sites except one I wanted to use.
Btw, Eclipse 3.5M6 has option to use only selected update site -- it is great help when updating/installing plugins. I cannot wait to see Eclipse 3.5 final released, just for this feature.
Eclipse plungins require Equinox UI for dependency.Please read Equinox installer .I hope can help you. : )