Community
Participate
Working Groups
Choosing "Restart" (which is all too easy when one is typing-away at code), restarts and then the error happens almost immediately once Eclipse has restarted. Dismissing the dialog seems to have no ill effects, though I do not believe I am using any recommenders. I'm happy to provide more information if it would be helpful. Just tell me what you need. Auto-filled bug message from Eclipse Oxygen below: Unresolved bundles: org.eclipse.recommenders.snipmatch org.eclipse.recommenders.snipmatch.rcp
Hi Christopher, Try updating your Eclipse installation using Help > Check for Updates. If the problem persists afterwards, additional information would help a lot in diagnosing this. Start Eclipse with the Host Osgi Console enabled. How to enable it depends on your operating system. Have a look at this Stackoverflow answer (and follow the given link for more information): https://stackoverflow.com/questions/16799200/how-to-get-the-host-osgi-console-for-eclipse Afterwards, in your Eclipse's main menu, select Window > Show View > Console. In the console view, in the top right, there is an icon of a window with a small 'plus' symbol. Click it and select Host Osgi Console. Please start Eclipse with the -console command line switch and enter the following in the OSGi console that then becomes available in your terminal window: diag org.eclipse.recommenders.snipmatch Then, copy & paste the output here. Thanks in advance.
Thanks, Johannes. One of the first things I did was to check for updates, and I was offered some unrelated updates (2.0-style plugin plug-in, VelocityEdit) and applied them. I restarted Eclipse when offered to do so after the update and almost immediately saw the same problem. I've enabled the console (macos easy: just launch with -console CLI arg). ======= WARNING: This console is connected to the current running instance of Eclipse! osgi> diag org.eclipse.recommenders.snipmatch org.eclipse.recommenders.snipmatch [759] Unresolved requirement: Require-Bundle: org.eclipse.recommenders.coordinates; bundle-version="[2.4.0,2.4.1)" osgi> ======= I did the same for the package with ".rcp" on the end and got the same response. A little more information about my installation: this was initially an install of Eclipse Neon (using Oomph, I think) which surprisingly upgraded itself to Oxygen. No problems with Oxygen other than this one. I'm happy to do a clean install to get past this irritation, but I'm also happy to suffer through it if it yields a fix for others.