I like to stay up-to-date with the latest Eclipse releases, often times using release candidates weeks before an actual release. The Eclipse release candidates, generally speaking, are top-notch and free of problems. So I was very surprised to discover a major problem with the 3.6 release almost immediately.
The problem was this: plugins did not appear to work. I dutifully installed my standard plugin set using the Update Manager but discovered no evidence of the effort after a restart. Subclipse? Missing. Mousefeed? FindBugs? nWire? Missing!
(Want to skip to the solution without reading more?)
Help > About > Installation Details showed they were installed but none were shown on Features or Plug-ins tabs. Apparently installed doesn’t mean installed in the typical sense of the word.
- starting eclipse with -clean didn’t seem to help
- starting eclipse with -consoleLog -debug didn’t turn up anything
- starting eclipse with -console and using the ss command on the osgi console did not turn up the wayward plugins
peer support via IRC
Misery loves company, as they say, so I went to #eclipse on IRC. After sharing my troubles and troubleshooting, a person with the nick paulweb515_ began helping me.
At this point, I determined my plugins were being installed in ~/.eclipse/.../features/ and ~/.eclipse/.../plugins/. Huh? What is this? Apparently that’s a feature of Eclipse. But I’m getting ahead of myself…
While in #eclipse I did some more extensive Google searching and turned up a bug report, titled Plugins install, but do not work, which seemed to mirror my problem.
The bug report indicated that Eclipse places plugins and features in ~/.eclipse/ when the user does not have sufficient permission for the eclipse program directory itself. As I wrote before, apparently that’s a feature. But, still, my plugins weren’t working!
My solution, then, is to install Eclipse in a location where the user has full rights. For Windows 7 users, a good location might be under the user’s home directory (%HOMEPATH%). Alternatively, the user could be granted full control of the Eclipse program directory.
While I’m glad my Eclipse is back to normal, I’m still disappointed in the amount of time wasted on the problem. And, unfortunately, I’ve not been able to determine if this ~/.eclipse/ feature is broken or if something else is going sideways.
Update: Looks like the author of nWire has posted about this issue.