I'd like to be able to edit both Ruby and Bash files natively in Eclipse Keppler. I also need Mylyn. The problem is, that installing ShellEd triggers dependency conflict:
Is there any way to use ShellEd together with Mylyn/Ruby? Is there a reason to issue a bug on ShellEd?
edit: This is a list of my istalled plugins:
The version of the DLTK Ruby tools you have installed is 2.0.0 which is very old (the current version in the Kepler repo is 5.0.0). ShellEd declares that it requires DLTK version 4.0.0 or higher, so you just need to upgrade to the latest DLTK Ruby version. That should be easy to do by selecting the Kepler repo when doing Install New Software.
It looks like the DLTK Mylyn Integration feature does not exist any more so you'll have to let it be uninstalled. That doesn't affect Mylyn in general, which should remain intact.
Related
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.
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
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.
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.
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.