Red Hat Bugzilla – Bug 825831
Only some plugins show up
Last modified: 2014-01-12 19:27:14 EST
Description of problem:
Since the update to Eclipse 4.2.0-0.22 on Friday (25 May), only some of the plugins seem active: that is, I can see editors, perspectives, and so on from JDT and from TeXlipse (for example), but nothing from CDT or fedorapackager. So if I click on a .h or a .spec file, it opens in an external editor.
Running with eclipse -clean -debug -consolelog, I see everything I should.
Version-Release number of selected component (if applicable):
Haven't tried -- but it happens every time I open Eclipse with this configuration
Here's a link to a zipped version of my ~/.eclipse directory:
Here's the output of rpm -qa eclipse*:
I'm looking into it.
Your .eclipse directory seems to be fine.
I need a .log file that can be found in your workspace/.metadata directory after you start eclipse with -clean.
The other thing I need is an output of:
eclipse -debug -clean -consolelog
It is necessary to start eclipse in the installation directory - it should give a really good dependencies resolution info.
Also, if you open a Plug-in Registry view, do you see cdt bundles loaded?
Is there anything else missing except the CDT?
(In reply to comment #2)
> Your .eclipse directory seems to be fine.
However: yesterday, I tried "eclipse -debug -clean -consolelog" and today, when I loaded Eclipse, the plug-ins were there. Then I copied the attached .eclipse directory back into place and re-started eclipse, and the plugins were gone again. So something in that ~/.eclipse triggers badness.
> I need a .log file that can be found in your workspace/.metadata directory
> after you start eclipse with -clean.
Running with "-clean", I don't see the problem any more. Do you still want the log?
Also, it seems that just "-clean" is enough to fix the problem with my .eclipse. If I run eclipse -clean, close, and then run regular eclipse, the problem goes away.
I'll attach the diff between my working and non-working .eclipse directories shortly.
> The other thing I need is an output of:
> cd /usr/lib64/eclipse
> eclipse -debug -clean -consolelog
> It is necessary to start eclipse in the installation directory - it should
> give a really good dependencies resolution info.
I'll attach that too.
> Also, if you open a Plug-in Registry view, do you see cdt bundles loaded?
> Is there anything else missing except the CDT?
At least the eclipse-fedorapackager stuff is also missing
Created attachment 587393 [details]
Output of eclipse -debug -clean -consolelog from installation directory
Created attachment 587394 [details]
diff between working and non-working ~/.eclipse directory
Two issues here:
1. !MESSAGE Unable to satisfy dependency from org.fedoraproject.eclipse.packager.feature.feature.group 0.3.2.201205241628 to javax.xml.bind 0.0.0.
It might be a bug in the fedorapackager which does not symlink the javax.xml.bind. Could you install eclipse-mylyn-commons and check if the problem goes away?
If yes, I will open a separate bug for this issue.
2. Some problems seem to be caused by net.sourceforge.vrapper.eclipse. Could you check if uninstalling it helps? Also, running eclipse without -clean could help.
Neither installing eclipse-mylyn-commons nor uninstalling eclipse-vrapper have any effect on the symptoms. However, running eclipse -clean once seems to fix things up -- after running that one time and closing eclipse, then regular runs of eclipse (without -clean) also find all of the plug-ins again.
I can reproduce the problem at will by copying my old ~/.eclipse (linked above) back into place.
I'm afraid there is nothing I can do about this issue right now, as it is related to Equinox caching, and it is impossible to clean user configuration at install time.
Running eclipse -clean is practically the only option that we have right now. I'll try to limit the number of future plugin content changes which are not reflected in the plugin version.