Eclipse on Mac doesn't allow to downgrade (E)Git - eclipse

I have updated my Eclipse for Committers to version 2021-12 (For MacOS), and found out that the default Git-plugin version installed is 6.0. Since Git deprecated some features who are still crucial to me, i tried to downgrade Git version to 5.11 (the last version i know that has the requested features).
But apparently Eclipse doesn't allow to uninstall any of it's Git add-ons, which is the first step in the downgrading process.
I tried to uninstall from different menu paths, but they all lead to failure. I also tried that with "Eclipse for Java developers" (non-committers), and with older versions of Eclipse, without success.
Does anyone know what can i do?
Thanks.

Like it says in the dialog, the Git Integration is required by something else you have installed. There's little unique about the "Eclipse for Committers" download, meaning if you can't uninstall something you want to uninstall, you can still start from the bare basics and then install more into it. You should start with an SDK download from https://download.eclipse.org/eclipse/downloads/ and then add the versions of software you actually want to it.

Related

How to upgrade from Eclipse Mars to Eclipse Neon?

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

Cannot install Mercurial on Eclipse Juno

Attempting to install Mercurial on Eclipse Java EE IDE Juno from
http://cbes.javaforge.com/update in the Install new software...
but,
"Cannot complete the install because one or more required items could not be found. Software being installed: codeBeamer Eclipse Studio (with Mylyn) 3.1.0.v201011161842 (org.codebeamer.eclipse.mylyn_feature.feature.group 3.1.0.v201011161842) Missing requirement: codeBeamer Eclipse Studio (with Mylyn) 3.1.0.v201011161842 (org.codebeamer.eclipse.mylyn_feature.feature.group 3.1.0.v201011161842) requires 'org.eclipse.mylyn_feature.feature.group 3.3.0' but it could not be found
I tried on Windows 7_64 and ubuntu 12.04_64. I even installed mylyn using the latest stable releases from http://download.eclipse.org/mylyn/releases/latest
Any Ideas?
Already browsed web and this site.
You could also try the update URL from the Google Code repository instead, which installs only MercurialEclipse.
+1 to installing from Google Code Repository.
Initially Eclipse wouldn't start because of problems with the older version of the plugin so to get past this simply removed the jar com.vectrace.MercurialEclipse_1.9.1.v201111302231.jar from the Eclipse plugins directory then uninstalled the existing plugin and re-installed from the link in smooth reggae's post.
All seems good so far.
The problem is, that the codeBeamer Eclipse Studio requires an older version of Mylyn (3.3.0), which isn't available for Juno.
But AFAIK you don't need the whole CBES, if you only need the Mercurial features. Try to select only MercurialEclipse, it should also be available in that update site.

Cannot complete the install because of a conflicting dependency

I am using eclipse helios (IDE for Java EE developers) 64 bit latest version
and when I am trying to update it from help>check for updates
I am getting the error:
Cannot complete the install because of a conflicting dependency
Why I am getting this error, and how can I solve it?
You are getting this because there is a conflicting dependency somewhere. For example, if you have plugin A that depends on dependency.X-1.0.0 installed, and try to install plugin B that depends on dependency.X-1.1.0, there is a conflict. When you check for updates, Eclipse will check all plugins and features you have installed in the past. Try to update one thing at a time to identify which update has a conflicting dependency.
Hope this helps!
Download bundles from here:
linux 64 bit vm: http://dl.google.com/android/adt/adt-bundle-linux-x86_64-20140702.zip
linux 32 bit vm: http://dl.google.com/android/adt/adt-bundle-linux-x86-20140702.zip
mac: http://dl.google.com/android/adt/adt-bundle-mac-x86_64-20140702.zip
win32: http://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
win64: http://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
Starting with ADT bundle 23.0.2, you should be able to update to future versions of ADT.
I couldnt get things working in the 'normal' update screen, but when going to 'About eclipse platform' screen and push the 'installation details' button. I got another screen, where you can select an installed plugin and update it.... in there it worked.
In there I first selected the plugin that seemed to be causing the conflict, and update it. Then the other one conflicting with this one... (the conflict in my case was between the android sdk and my java development tools)
Don't ask me why and what's the difference.... this option might be of help to others...
If running on Windows 7, these errors can often be resolved by running Eclipse as Administrator, then update. https://bugs.eclipse.org/bugs/show_bug.cgi?id=339659
I Could resolve it by checking already installed plugins at where it was giving me this error. I just uninstalled all the plugins which had conflicting dependency and try to install the updates. It worked well.!
check the marked area in this linked image
Generally, why it should happen is that while updating plugins lately,they have evolved 2-3 updates and during which plugins have introduced some new functions that have to be installed and also are to be updated. This thing creates conflicts of dependency. Eclipse tries to update which is not already existing/installed and it also tells install it first which creates conflicts.
So, when you uninstall the plugins, now it installs the latest plugins rather then updating. it means you updating eclipse plugins manually(by uninstalling older and installing latest). This may happen if you have skipped 2-3 updates and now looking for latest update.
I agree with Michel.iamit. I tried all other options of updating the ADT and it did not work. With Michel's solution, my environment did not work and it complained about the conflict.
So here is what I did and got it to work:
First uninstall all ADP Plugins.
Then check for updates and it will prompt you regarding the missing plugins.
Select all, accept all licences and proceeed.
Hope this helps someone.
I solved this problem by downloading the latest ADT release from following urls
linux 64 bit vm:
http://dl.google.com/android/adt/adt-bundle-linux-x86_64-20140702.zip
linux 32 bit vm:
http://dl.google.com/android/adt/adt-bundle-linux-x86-20140702.zip
mac:
http://dl.google.com/android/adt/adt-bundle-mac-x86_64-20140702.zip
win32:
http://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
win64:
http://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
After opening eclipse IDE go to Help ->Install New Software->Add
Name = ADT plugin ,
location = link and select all Developer Tools . After installation completed please restart your ide and all the bugs get solved now.
I resolved this issue by running eclipse as root, and then installing the updates from Help>Install New Software and adding the latest update version to the download list (http://download.eclipse.org/eclipse/updates/4.4). Not sure if this is the best way, but it worked to go from Indigo (3.8) to Luna (4.4). I'm doing this on Ubuntu 14.04 x64

What is the best way to upgrade Eclipse 3.6 to 3.7 (or a subsequent version)?

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 can't update Eclipse 3.5 up to 3.6. If I install 3.6 over it, will I retain my plugins?

When I go to Help->Check for Updates in Eclipse, it checks all the repositories and says "Nothing to update", but my Eclipse version is 3.5.2.R35... I am trying to install the eclim plugin and that requires Eclipse 3.6.x.
If I install Eclipse 3.6 from the eclipse.org website, would that preserve the plugins and configuration I currently have installed?
Thanks!
-M
Usually changes between minor versions (3.x) are big enough to break any plugin functionality. You should find out whether specific plugins you're using support newer version of Eclipse.
You can always download a newer version of Eclipse and install it to different directory and run it from there to test your plugins (which you'll have to install once again to a newer platform). You'll always be able to go back to the older version.