Community
Participate
Working Groups
I've just updated from Neon to Neon.1, now all update sites are lost. The list of "Available Software Sites" is completely empty which means I'm locked out of any future updates. -- Configuration Details -- Product: Eclipse 4.6.1.20160912-1200 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.platform 4.6.1.v20160907-1200
Lowering the bug severity as there is no crash, loss of data or severe memory leak. - https://wiki.eclipse.org/Eclipse/Bug_Tracking#Severity
Created attachment 264559 [details] Issue not reproducible. I can not reproduce the issue with these steps: - get a fresh Eclipse Neon R - add an update site, i.e. WindowBuilder - select Help > Check for Updates - after the update is complete verify the update sites are still in place. Could you please tell us the steps to reproduce the issue on your system?
I cannot tell if it is reproducible as I've now upgraded. However what I noticed was that one file seemed to be destroyed by the update: p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.jee.profile\.data\.settings\org.eclipse.equinox.p2.metadata.repository.prefs This file was very small after the update and contained no references anymore to the repositories defined in org.eclipse.equinox.p2.artifact.repository.prefs The latter still existed and had all the information in it, but the metadata file only contained around 15 lines (I don't have a copy anymore) containing not a single http repository reference. Maybe that helps
We can't do much without further details.
Well it just happened again when trying to upgrade from Neon.1 to Neon.2 on one of my installations. After searching for updates and installing everything, I restarted Neon. I instantly saw that there was something wrong as the splash screen still showed "Neon.1" and after rechecking for updates I was told that there were no update sites, and surely, that file was reset again. "About Eclipse" however shows me "Version: Neon.2 Release (4.6.2)", but the splash screen still shows Neon.1 on this installation. Maybe there was something going wrong during the update? Are there any logs somewhere from the update? In the configuration tab I also still see that the splash is taken from the Neon.1 plugin: -showsplash D:\Eclipse\Eclipse-4.6-Neon\\plugins\org.eclipse.platform_4.6.1.v20160907-1200\splash.bmp This is extremely annoying... :-(
I confirm that this happens when upgrading from Neon.1 to Neon.2.
I can confirm that it happens consistently when updating or installing new software on any of the versions of Neon that I have tried so far. (C/C++, 64-bit, Windows 7) Very easy to reproduce: 1. install Neon 2. check "Available Software Sites" list is populated 3. run Help -> Check for Updates 4. update software accepting all defaults 5. after Eclipse restarts, run Help -> Check for Updates again. This time result is dialog stating there are no update sites to search and the "Available Software Sites" list is empty. I also found that if I use the export button in step 2, after installation and before the update, I can later restore it. Since this bug hasn't been looked at in a while, I will try to find the time to open a new bug to hopefully find a fix for this issue.
(In reply to Dale Wityshyn from comment #7) Seeing virtually same behaviour as you. I submitted the following: Bug 516915 - Available Software Sites cleared after first launch
BUMP! Same problem for a fresh GNU MCU Eclipse. Both for Neon.3: https://github.com/gnu-mcu-eclipse/org.eclipse.epp.packages/releases/tag/v4.2.1-201711101735 and Oxygen.1a: https://github.com/gnu-mcu-eclipse/org.eclipse.epp.packages/releases/tag/v4.2.1-20171110-o1a I see the milestone is Photon. Please, consider this as a very annoying bug and move the milestone back or at least back-merge the fix.
I also experienced this bug when upgrading Oxygen.2 to Oxygen.3. As I manage the Eclipse versions in Subversion I noticed that p2/org.eclipse.equinox.p2.engine/profileRegistry/epp.package.jee.profile/.data/.settings/org.eclipse.equinox.p2.metadata.repository.prefs was reset during the upgrade. This should definitely be fixed! I'm using JEE version x86_64 on Windows.
I confirm the bug reappeared after upgrading Oxygen.2 to Oxygen.3
The same thing happened when updating Photom from 4.8 M4 to 4.8 M6.
I have not seen this myself. I usually update 1-2 times a week to the latest I-Builds. Not sure if that changes things since I don't use the EPPs, but instead manage my own install based off the latest. Moving out of Photon.
This just happened to me after updating from Eclipse 2018-09 M2 to 2018-09 M3 (Windows 10). I opened Eclipse today and asked it to check for updated. It politely told me there were no update states. They are gone. Empty. None. Nada. Zero. This was a brand new installation that had been installed and upgraded only a couple of times within the last few weeks because of Bug 536806. * Install a clean distribution of Eclipse IDE for Java EE Developers Photon, e.g. eclipse-jee-photon-R-win32-x86_64.zip. * Add the http://download.eclipse.org/releases/2018-09/ site and do an update. Eclipse is getting less stable and less predictable in its update process.
Above I wanted to say "check for updates" and "no update sites", but your bug system doesn't let me edit my comments.
Same here. After updating from Eclipse 2018-09 to 2018-12 (Windows 10). All update sites are gone.
After updating from Eclipse 2018-09 to 2018-12 on Linux, all update sites are gone.
Same here after updating from Eclipse 2018-09 to 2018-12 on Win7x64. Is there an file available for import?
I also ran into this problem. The strange part is that there is nothing in the log. As this is a pretty only bug that affects nearly every Eclipse from the past years I would recommend to increase logging in the component that is responsible for loading and verifying the update sites so that we can finally fix this bug. BTW: Does anybody know why the update sites are stored twice? If I add an entry I find identical entries in the following files: Eclipse\p2\org.eclipse.equinox.p2.engine\profileRegistry\epp.package.jee.profile\.data\.settings\ org.eclipse.equinox.p2.artifact.repository.prefs org.eclipse.equinox.p2.metadata.repository.prefs When I look at those two files on the affected Eclipse installation the org.eclipse.equinox.p2.artifact.repository.prefs looks good. However the "metadata" file contains only a few entries. As this bug occurs only occasionally I would place my bet that there is a race condition in the code populating the data that is later written to the file or in the write process itself.
Happened to me too after the update from 2018-09 to 2018-12. How can I get my list back?
Does anyone know how to fix the issue?
Same here after updating to 2019-03. All my update sites are lost. I was able to restore most of them by manually searching for "/uri=" in an old backup of the .repository.prefs file, but more recent ones I had to Google and add again. Not sure if I have all of them again, but probably I will notice when plugins start to get incompatible and I am not getting offered any updates. That eclipse installation is quite an old one, which was already updated from some older version I don't remember to Eclipse Neon, and so on. The installation definitely did not use the Oomph Installers (at that time, they did not work if your main user did not have Administrator privileges), but was installed by manually extracting the eclipse Folder to Program Files. I did the update by starting Eclipse as Administrator (on Windows 10), adding https://download.eclipse.org/releases/2019-03/ to the update sites, unchecking a few old ones, and then checking for updates. After restart of Eclipse (and upgrading the workspace), update sites were gone. (All previous updates were done the same way, and update sites have not been gone before). Sorry that I cannot provide any information about how to reproduce - I hope it won't happen again, but I will probably export my update sites before each future update just to save me the extra work next time.
In case it matters: This was the first update I did with Java 11 as my main JRE (before I always used Java 8). I regularly got the warning message described in Bug #539545, but apart from that (and from the lost update sites) Eclipse works fine with Java 11.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
