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
Related
I am looking for steps to upgrade my current Eclipse version (Mars) to latest version (Oxygen) because I have been using Mars for past long time so that contains all the settings, plugins and all the histories so I would like to retain the same and also upgrade to new version.
Is this possible?
Note: It can be any type of Eclipse for any kind of development like Java, C/C++, PHP, JavaScript and Testers.
In Window > Preferences: Install/Update > Available Software Site make sure that the Latest Eclipse Simultaneous Release (or Latest Eclipse Release) update site exists and is checked. Otherwise (in older versions or when this update site has been removed in newer versions), click Add..., enter the update site location https://download.eclipse.org/releases/latest and click OK.
Help > Check for Updates
See also Eclipse Wiki - FAQ How do I upgrade Eclipse IDE?
This might be useful.
https://wiki.eclipse.org/FAQ_How_do_I_upgrade_Eclipse_IDE%3F
There are some package structural changes from Eclipse Neon.
I don't think updating from Update Site will update the eclipse.ini file: you need to fix it.
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.500.v20170531-1133
However, if you simply want to keep your preferences and your plugin, I suggest you to use Eclipse for that:
In Oxygen.1 (or the updated Eclipse), you can install feature/plugins
using an existing installation (go to File > Import then select *Install > From Existing Installation)
using an exported software item (go to File > Import then select *Install > Install Software Items from File)
For the second option, you need to export it first on the previous Eclipse using File > Export > Install > Installed Software Items to File.
Note: the Eclipse directory store little configuration (at least, it store the known workspaces/update site). This link here might be of interest.
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
When I select "Help->Check for Updates" in eclipse, I get the following error message at the bottom of the window. From this message "Only one of the following can be installed at once: " it appears I have multiple copies of the same component installed. Under "About Eclipse SDK=>Installation Details" I found at least two instances of Equinox P2 Provisioning: under "Eclipse SDK" and "PHP Development Tools".
Any suggestions on how to get this resolved would be much appreciated.
I'm running eclipse helios 3.6.1 on CentOS 5.2.
Cannot complete the install because of a conflicting dependency.
Software being installed: Eclipse SDK 3.6.2.M20110210-1200 (org.eclipse.sdk.ide 3.6.2.M20110210-1200)
Software currently installed: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
Only one of the following can be installed at once:
Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr)
Equinox p2 Provisioning 2.0.0.v20100503-897HFZ-FdHjO2NQo0sD_Nt (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.0.v20100503-897HFZ-FdHjO2NQo0sD_Nt)
Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628 (org.eclipse.equinox.p2.user.ui.feature.jar 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628)
Cannot satisfy dependency:
From: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
To: org.eclipse.equinox.p2.user.ui.feature.jar [2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr]
Cannot satisfy dependency:
From: Equinox p2 Provisioning 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628 (org.eclipse.equinox.p2.user.ui.feature.group 2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628)
To: org.eclipse.equinox.p2.user.ui.feature.jar [2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628]
Cannot satisfy dependency:
From: Eclipse SDK 3.6.2.M20110210-1200 (org.eclipse.sdk.ide 3.6.2.M20110210-1200)
To: org.eclipse.equinox.p2.user.ui.feature.group [2.0.1.r361_v20100903-897HFa-FX0z-z-ntoaavz0JPX628]
Update 9/15: I read somewhere that this may be due to a permissions issue and that I should run eclipse as root and perform the update. I was indeed able to complete the 3.6.2 SDK update as root but then afterwards all of my add-on components (e.g. subclipse, PDT, etc.) were gone.
You are getting this message because you are trying to install into a read-only (shared) location. The indication is at this line:
Software currently installed: Shared profile 1.0.0.1288623084982 (SharedProfile_SDKProfile 1.0.0.1288623084982)
The reason why there is a failure is that your install plan would remove an old version of a feature that is part of the shared install. Since a shared install cannot be changed, you get the conflicting dependency.
As it happens, I am working on a patch for exactly this bug. See:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=332158
The fix would not allow you to install in this situation, but it would at least provide a better error message for you.
I got this message or something similar because I had installed Eclipse to my C: drive on Windows 7. Trying to do an update required escalation but Eclipse wasn't prompting me. When I restarted Eclipse using "Run as Administrator", it had the proper permissions to continue and it let me upgrade.
Cannot satisfy dependency:
From: Eclipse SDK 3.6.2.M20110210-1200
It needs a dependency that only exists in the update site for Helios 3.6.2 and you are running 3.6.1. You can either upgrade to the latest version of Helios (or better yet, Indigo) or add the update sites. I don't know the URL's off the top of my head, but you can try this method:
Download a fresh copy of Helios and install it to a separate folder. Open up help>install new software and click "available software sites". Then export the default sites and import them into your existing Eclipse installation. Your plugins should now update correctly.
EDIT: add this to your update sites: http://download.eclipse.org/eclipse/updates/3.6/
Note that shared install have now (upcoming Eclipse 4.3, 2013) a way to:
Detect shared install changes:
When Eclipse is running in a read-only folder (also known as shared install) and the read-only installation has changed (e.g. new plugins installed, new version of Eclipse installed), Eclipse will now detect this change and warn that your personal additional plugins have been uninstalled.
Provide a Migration Wizard:
Eclipse now includes a migration wizard to help users through the re-ininstallation of their plug-ins.
This wizard is presented in two situations.
First, when a read-only installation of Eclipse is being changed (i.e. Eclipse is being updated or plugins are added / remove),
second when a new read-only installation of Eclipse is run for the first time.
See also "Shared installs just got better!" for more:
Building on this support, we've also decided to assist users in re-importing their plug-ins from a previous read-only installation.
The reason is simple, many corporations chose to deploy new versions of Eclipse in different folders. This is required to give teams the ability to adopt Eclipse at their own pace, but it also means that when users start using a new Eclipse install, they need to re-install the plug-ins they had installed on their own.
Of course users could use the import/export feature provided by p2, but the time wasted by the user wondering why the plug-ins have vanished and then figuring out what to re-install can be significant, which is why in such situation we are also presenting the migration wizard.
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've got my Eclipse 3.4 envirnoment set up nice and cozy the way I like it. Took me some time too, to find all the plugins (Mylin, PDT, Subclipse), set all the settings, etc. Now I see that some of the plugins (like PDT) only support 3.5 in their latest versions.
Is it possible to update from 3.4 to 3.5? I'd hate to do it all again.
I read in some mailing list where they noted that it's possible, but the conversation trailed off in another direction. Google wasn't much help, and Eclipse's documentation either.
All of your settings are actually stored as part of your workspace. So you could do a fresh install of the latest version of Eclipse, add the extra plugins that you want (many of which will have newer versions for Eclipse 3.5) and when you launch, just make sure you point to your old workspace.
Help -> Software Updates... -> Available Software tab -> Add Site...
Enter the update site for the Galileo (3.5) release train: http://download.eclipse.org/releases/galileo
Now go back to the Installed Software tab and click the Update... button.
After some computation you should be presented with a list of available updates (or some cryptic errors about how your current environment cannot be updated due to compatibility issues).
This is what I did.
1.- My workspace was in c:\Users\me\workspace.
I copied this folder to c:\users\me\eclipse\workspace-3.4 and to c:\users\me\eclipse\workspace-3.5
So now I have twice the same, just with different names.
2.- Extracted eclipse-SDK-3.5-win32.zip to C:\program files\eclipse-SDK-3.5-win32
3.- Run Eclipse 3.4 and changed the workspace from c:\Users\me\workspace to c:\users\me\eclipse\workspace-3.4. Then I closed Eclipse.
4.- Run Eclipse 3.5 and selected c:\users\me\eclipse\workspace-3.5 as the workspace location (you can also use the -data argument I think).
5.- Downloaded and installed the PDT plugin (I develop in PHP).
And "Voila", now I'm able to run Eclipse 3.4 and 3.5.
BTW, even if I had to install the PDT plug in, I didn't had to touch the configuration. It took the former one from the workspace folder.
There is some information at help.eclipse.org/galileo/index.jsp, look in Workbench User Guide\Tasks\Upgrading Eclipse.