Community
Participate
Working Groups
Message after clicking the dialog which contains an option like "Show me more details", but i forgot the exact text. But i think you know what i mean: `An error occurred while collecting items to be installed session context was:(profile=J__Development_IDE_Eclipse_jee-2018-09_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,com.sun.jna,4.5.1.v20190425-1842 No repository found containing: osgi.bundle,com.sun.jna.platform,4.5.1.v20190425-1842 No repository found containing: osgi.bundle,org.apache.httpcomponents.httpclient.win,4.5.6.v20190213-1947 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core.win32,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.help.ui,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui.css,1.7.7.v20190521-1752 No repository found containing: org.eclipse.update.feature,org.eclipse.epp.mpc,1.7.7.v20190521-1752` Regards, Jan
...i don't known it's a general eclipse problem? - Or just on eclipse java? - Or just on eclipse J2EE...? Screenshot of the dialog here: https://i.ibb.co/SmRM83g/Unbenannt.jpg Regards, Jan
How to bypass that problem, are there any workarounds? Thx for feedback, Jan
(In reply to Jan Marti from comment #1) > ...i don't known it's a general eclipse problem? > > - Or just on eclipse java? > - Or just on eclipse J2EE...? > > Screenshot of the dialog here: > https://i.ibb.co/SmRM83g/Unbenannt.jpg > > > Regards, > Jan One thing I know is, that this is not caused by JDT. That said, an error without context doesn't tell much.
OK i was not sure which option i have to select? Maybe you can tell me or change it by yourself if you are an eclipse developer?
"That said, an error without context doesn't tell much." So please tell me the additional informations you need! ;-)
So it seems, i'm not the only one. The problem orrurs when i use one of each update URLs, or both: - 2018-09: http://download.eclipse.org/releases/2018-09 - 2018-09: http://download.eclipse.org/releases/2018-09/201809191002 So what's the difference between that URLs? If you also haev any questions regarding that bug, so please don't hestitate to ask me! Best regards from Switzerland, Jan
And, so it seems, i'm not the only one person with that problem: https://www.eclipse.org/forums/index.php/t/1100847/
It seems it has nothing to do with the default eclipse update URLs. When i uncheck http://download.eclipse.org/mpc/releases/1.7.7 the problem is "gone"... But that's not an adequate solution for that issue...
Possible Workaround: Change update URL to 1.7.6 And it was not ME, i never added that 1.7.7 version entry - so it must be a bug in my opinion.
Maybe it's indeed an issue with repositories of the market place client, moving to them.
OK, market place client 1.7.6 seems to works, so that can be used as a workaround? But why version 1.7.7 was saved in my update url list? I think that was not me, so that eclipse version will be devlivered with an invalid marketplace update url - which is a bug (or issue...)
UPDATE: The marketplace client seems to be a lil piece of c**p, and adds the new and buggy 1.7.7 version update url automatically to the eclipse url list... Best regards, Jan
*** Bug 551641 has been marked as a duplicate of this bug. ***
*** Bug 548197 has been marked as a duplicate of this bug. ***
I was finally able to reproduce the problem: - I installed eclipse 2018-09 JEE (https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2018-09/R/eclipse-jee-2018-09-win32.zip). - I opened the MPC without updating it. - The update mechanism of MPC adds the update site of the newest compatible version: http://download.eclipse.org/mpc/releases/1.7.7 - I manually added the 2019-03 update site (http://download.eclipse.org/releases/2019-03/) which contains MPC version 1.7.5.v20190313-2005 and called “Check for Updates”. - The new eclipse version and MPC version 1.7.7.v20190521-1752 are scheduled for installation. - I am able to start the installation but receive the known error message after a short while: An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,com.sun.jna,4.5.1.v20190425-1842 No repository found containing: osgi.bundle,com.sun.jna.platform,4.5.1.v20190425-1842 No repository found containing: osgi.bundle,org.apache.httpcomponents.httpclient.win,4.5.6.v20190213-1947 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.core.win32,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.help.ui,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.eclipse.epp.mpc.ui.css,1.7.7.v20190521-1752 No repository found containing: osgi.bundle,org.apache.httpcomponents.httpclient,4.5.6.v20190503-0009 No repository found containing: org.eclipse.update.feature,org.eclipse.epp.mpc,1.7.7.v20190521-1752 Updating only MPC to 1.7.7 does not work directly after the above steps but works after restart of eclipse and then updating eclipse works like charm. This does not look like a MPC problem.
*** Bug 560006 has been marked as a duplicate of this bug. ***
I have found the issue. For the update check, only the metadata repo is loaded, since the artifact repo is not yet needed at that point. This is faster, and harmless in cases where the repo is already in the Available Software Sites list (as both metadata and artifact repo). However, it breaks if it wasn't there previously (as might happen with version-specific sites, or in case of MPC, if it was installed through a different channel), because this leaves us with a metadata repo which isn't removed after the update check, and no corresponding artifact repo. I'll have a fix ready for RC2, which will clean up properly after the update check, not leaving broken repos around.
(In reply to Carsten Reckord from comment #17) > However, it breaks if it wasn't there previously (as might happen with > version-specific sites, or in case of MPC, if it was installed through a > different channel), because this leaves us with a metadata repo which isn't > removed after the update check, and no corresponding artifact repo. Regarding the scope of this bug: This isn't just about MPC checking for updates of itself. There is no special self update routine. Instead, MPC checks for updates of all Marketplace listings that are installed locally. It just happens to present its own updates a bit differently from the rest. This means that whenever a Marketplace listing would put out a new version under a new update site url, this bug would affect everyone who has that listing installed. Fortunately, it looks like P2 does a bit of self-healing, because the missing Artifact repo seems to appear after an Eclipse restart. Though I haven't tracked down how/where that happens yet.
As a workaround, removing the offending repository in Available Software Sites, and immediately adding it manually again, should also fix the issue, since then both artifact and metadata repo are created.
Hey everyone, I've pushed a fix in commit 1f992ae2d42ca49a3de5be523083d5bc0ffa1b9b yesterday and Leif was so kind to test and publish a build to http://download.eclipse.org/mpc/nightly/latest. Please take it for a spin. The fix will be contributed to 2020-03 RC2. Unfortunately, getting P2 to do sane things can be a challenge at time, and so with RC2 at our doorsteps, I took the safe route and completely loaded the artifact repo alongside the metadata one, although it's not really needed at that point. This makes the update check longer than necessary. I plan to revisit this with the release out of the door and see if we can do better safely.
I tested with several versions and was not able to reproduce the problem. Thanks Carsten for the fix.
(In reply to Carsten Reckord from comment #20) > Hey everyone, I've pushed a fix in commit > 1f992ae2d42ca49a3de5be523083d5bc0ffa1b9b yesterday and Leif was so kind to > test and publish a build to http://download.eclipse.org/mpc/nightly/latest. > Please take it for a spin. > > The fix will be contributed to 2020-03 RC2. > > Unfortunately, getting P2 to do sane things can be a challenge at time, and > so with RC2 at our doorsteps, I took the safe route and completely loaded > the artifact repo alongside the metadata one, although it's not really > needed at that point. This makes the update check longer than necessary. I > plan to revisit this with the release out of the door and see if we can do > better safely. Hello, Glad u guys fixed it, but I don't understand how you did it. I tried following the chatter and in install/update, I ran your http://download.eclipse.org/mpc/nightly/latest. I even tried updating both marketplace and mylyn. I now have about a few dozen more of the osgi repos not found. I am just about ready to deinstall eclipse, but realized that a reinstall will take a day off work. Not all of us are eclipse-gurus like you, some help for ordinary users of eclipse and e(fx)clipse would be very much appreciated :) An error occurred while collecting items to be installed session context was:(profile=E__Users_acina_eclipse_java-2019-03_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.eclipse.mylyn.bugzilla.core,3.25.0.v20190128-2356 No repository found containing: osgi.bundle,org.eclipse.mylyn.bugzilla.ide,3.25.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.bugzilla.ui,3.25.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.builds.core,1.17.0.v20190129-0014 No repository found containing: osgi.bundle,org.eclipse.mylyn.builds.ui,1.17.0.v20190111-2151 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.core,3.25.0.v20190131-2250 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.identity.core,1.17.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.net,3.25.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.notifications.core,1.17.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.notifications.feed,1.17.0.v20190115-0848 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.notifications.ui,1.17.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.repositories.core,1.17.0.v20180628-1730 No repository found containing: osgi.bundle,org.eclipse.mylyn.commons.repositories.http.core,1.17.0.v20190116-
Hi Arthur, sorry to hear that the fix does not seem to work for you. Could you provide some more details? - What version of Eclipse are you using? - Were you able to update MPC? What is the exact version of your installed MPC? (Find out via Help -> Install New Software -> What is already installed? -> Search for Marketplace Client) - Were you already able to update mylyn? - Which steps led you to the posted error message? This information would really help use to locate the bug. As a workaround, have you tried to remove and re-add the mylyn and bugzilla update site via Window -> Preferences -> Install/Update -> Available Software Sites?
Hi Arthur, I have just seen in your error message that you are using Eclipse 2019-03. The newest MPC is only compatible with Eclipse 2019-09 and higher. But I think the workaround with removing and re-adding the update sites should work for you.
Hi and thx for responding. I disabled Mylyn (I assume bugzilla is integrated with it), then re-enabled it. Then, I ran "check for updates" and got the same error msg "Updating Software has encountered a problem" Now there are even more of these "no repos found containing:osgi.bundle, org.eclipse.mylyn.ide....,3.25.0v20180628-...."
(In reply to Leif Geiger from comment #24) > Hi Arthur, > > I have just seen in your error message that you are using Eclipse 2019-03. > The newest MPC is only compatible with Eclipse 2019-09 and higher. But I > think the workaround with removing and re-adding the update sites should > work for you. I have now deinstalled and reinstalled ver 2019-12, reloaded JavaFX and Mylyn (again I assumed Bugzilla is part of Mylyn b/c it makes sense). That got rid of the dozens of .osgi.bundle error messages. BUT now I have this new error msg: "No repos found at http://download.eclipse.org/efxclipse/updates-released/3.6.0" That is the version of FX I have installed. What do I do next? Is it a show-stopper, will it impact on my javaFX development?
Unfortunately I have more troubles: I have just installed Mylyn and everytime I start up Eclipse, it throws this error message: "Initializing Eclipse Error Reporting System has encountered a problem" "An internal error occurred during: Initializing Eclipse Error Reporting System." Unfortunately I cannot switch to another IDE mid-stream in a project, so any help would be much appreciated.
Hi Artur, sorry for the late reply. Concerning your problems with the FX repo. The provided URL does not provide an update site. The correct path would be http://download.eclipse.org/efxclipse/updates-released/3.6.0/site/. I don't think this is a show stopper, but it might hinder you to update efxclipse. You can try to correct the URL of the update site via Window -> Preferences -> Install/Update -> Available Software Sites. Concerning your Mylyn problems: It seems that your Mylyn version is using a deprecated error reporting mechanism. Try to update Mylyn or raise a new ticket for Mylyn.
