When I update the Eclipse Kepler to Mars then I receive error like below mentioned, please guide how to update this.
An error occurred while uninstalling
session context was:(profile=epp.package.standard, phase=org.eclipse.equinox.internal.p2.engine.phases.Uninstall, operand=[R]org.eclipse.rcp.configuration_root.win32.win32.x86_64 1.0.0.v20130521-1847 --> null, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CleanupzipAction).
Backup of file D:\Java\eclipse\eclipse\eclipse.exe failed.
Can not remove : D:\Java\eclipse\eclipse\eclipse.exe
In theory updating across major versions should work, but not necessarily across two releases (Kepler -> Mars is skipping Luna).
The recommended way to upgrade across major releases is to download the new version and install it into a separate location, then point it to your existing workspace. If you had third-party plug-ins installed you'll have to re-install them into the new Eclipse (which might require updated versions of those plug-ins, too).
Do not extract the new version on top of your existing Eclipse - that won't work and will cause problems.
Related
I have an Oomph setup for installing Eclipse 2018-12 with a few specific plugins.
In the setup I had to restrict some plugins to older versions, because all later versions of these plugins are incompatible with our build environment.
Eclipse automatically detects new plugin versions periodically and suggest to update these plugin. These new versions are certainly compatible with Eclipse. Technically no other plugin depends on these older plugin versions so I understand why Eclipse sees them as outdated and suggest to update. But since that would break our builds, I would like to prevent Eclipse from trying to update them.
Is there any configuration I can set during the installer to prevent certain plugin updates? Or do I have to completely disable automatic updates?
I have Eclipse 2018-09. My impressions was that Eclipse was moving to a rolling quarterly release, and by that I presumed I'd magically be offered updates every quarter to the newest. But now that 2018-12 is out, my instance does not detect any new updates.
Looking at the update sites in Windows -> Preferences, Install/Update -> Available Software Sites (incompletely listed below), I notice they seemed to be pinned to specific versions:
The Eclipse Project Updates: http://download.eclipse.org/eclipse/updates/4.9
The Eclipse Project Updates: http://download.eclipse.org/eclipse/updates/4.9/categories
Eclipse Project Repository for 2018-09: http://download.eclipse.org/eclipse/updates/4.9/R-4.9-201809060745
2018-09: http://download.eclipse.org/releases/2018-09
Oracle Enterprise Pack for Eclipse 12.2.1.8 Dependencies: http://download.oracle.com/otn_software/oepe/12.2.1.8/oxygen/repository/dependencies/
I've noticed there is also now an Eclipse Installer, which says it is "The easiest way to install and update your Eclipse Development Environment.". However, there is no description of updating, and when running it and pointing to the existing folder for 2018-09 (yes, I made a backup first to be safe), it does not update that folder but instead just creates a new sub-folder under the existing 2018-09 version called "eclipse" with presumably a complete copy of the new eclipse. So that's a failed attempt.
What is the recommended way of upgrading from 2018-09 to 2018-12? Is it:
Manually download a new copy of Eclipse and spend hours configuring it to hopefully be almost the same as the configurations in 2018-09
Run the Eclipse installer in some other manner than I already have.
Manually updating the update sites (to what values?). If the so, is there a way to specify to always use the latest on the update train?
Other?
See Eclipse FAQ - Always enable major upgrades:
To always enable major upgrades of your IDE once and for all:
from the Available Software Sites preference page
enable the Latest Eclipse release http://download.eclipse.org/releases/latest repository by ticking the checkbox.
Apply and Close
Check for updates
The similar workflow can be used to hide and disable automatic
proposal of major upgrades.
To my knowledge, the update site http://download.eclipse.org/releases/latest exists since Eclipse Photon (4.8) in Window > Preferences: Install/Update > Available Software Sites but is not checked by default.
If you want to change the default of this preference, vote for or comment on Eclipse bug 539281 - Enable http://download.eclipse.org/releases/latest by default.
The two advantages of using the Eclipse Installer over the direct installation of one or more IDE packages are:
The Eclipse Installer saves disk space when installing multiple IDE packages (by using a shared pool for the plug-ins of all IDE packages)
The Eclipse Installer makes it easier to contribute to an Eclipse project (advanced mode).
Another way to install Eclipse 2018-12 is to use Chocolatey on Windows. Eclipse 2018-12 corresponds to version 4.10.
PS C:> choco list eclipse
Chocolatey v0.10.11
eclipse 4.10 [Approved]
...
PS C:> choco install eclipse
...
But this won't do an in-place upgrade.
Go to Window-> Preferences -> Install/Update -> Available Software Sites
First, if exists remove duplicate sites
Second, click to eclipse related update sites and Reload
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
I am beside myself with this error and can't make any progress until I get past this issue.
I have the latest STS (Spring Tool Source) 3.7.1 specifically for Eclipse Mars 4.5.1. I deleted all my old versions of STS, and deleted my old .eclipse file as well since I wanted this to be a fresh install. I also went into my c:\Users\Tom Holmes\AppData folders and removed all traces of 'Spring Tool Suite'.
I installed the new latest STS 3.7.1 for Eclipse (Mars) 4.5.1 and pulled down the latest Subclipse for the Eclipse (Mars) 4.5.1. I opened to my old work space which was fine before, and now whenever I try to use STS to run a maven build I get the error listed below.
Error: Could not find or load main class Holmes.sts-3.7.1.RELEASE.configuration.org.eclipse.osgi.25.0..cp.;.C:.Users.Tom
I have tried everything I can think of to re-loading the projects into a new workspace, to deleting the projects and re-downloading them.
Ultimately I find in the workspace .metadata plugins directory under m2e.eclipse.core there are no lifecycle mappings? Does that matter?
How can I re-create this, or is this more of a maven/sts problem?
So, here is what I found ... Since STS 3.7.1, specifically for Eclipse (Mars) 4.5.1 was the issue ... I tried several other versions of STS.
I tried STS 3.7.0 for Eclipse (Mars) 4.5.1 which does work. When I installed this, I immediately got notified that there was an update ready. The update was specifically for the m2e Maven-Eclipse Integration.
I also tried 3.7.0 for Eclipse (Juno?) 4.2.2 which also does work, and again this was looking for an update, and again was for m2e Maven-Eclipse Integration.
My feeling is that, specifically STS 3.7.1 for Eclipse (Mars) 4.5.1 was broken as far as the m2e plugin. Since the m2e changes are embedded in this latest version, something must not have been right. The other versions that I downloaded and installed all worked fine. For any of these versions, there was this upgrade for the m2e (Maven-Eclipse) integration plugin ... but in this case, the update worked.
You know, I like STS, I think it works great. After updating several times, like anything else, it can get "jinky" and then I decide that maybe I should just download a new fresh copy of the tool which usually works great.
Clearly pulling this update into the latest version just didn't mesh well. But now I am up and running, and hopefully SpringSource will fix this issue.
I really hope this helps someone else out.
I would recommend installing a regular Eclipse distribution and then installing STS as a plugin. There should be plenty of instructions online that explain how to do it. I've been using this approach for years and never had any problems.
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.