It turns out my build script was halfway there with regards to
building against features installed in the eclipse.local dir. The
build script would recognize the features installed, but it wasn't
adding the eclipse.local jars to the classpath when building. I just
committed a fix[1] for that.
> > Let me know if that works and if not, let me know what the error is.
> >
>
> I don't get an error message, and it LOOKS like everything is as it should
> be (as far as I know, I have no idea how Eclipse works under the hood), but
> still eclimd does not show in the list of views. Also, "Vim" does not show
> up in the "Open With" menu for source files.
Unfortunately, eclipse can be very finicky. For some reason I never
manage to run into problems, but I do get reports from users about
new plugins no longer registering properly and requiring a fresh
eclipse install to get them working again.
I just went through the following steps on my ubuntu VM (12.04)
without any issues:
1. removed any local eclipse files so that my env is hopefully back to
a stock state ($ rm -r ~/.eclipse)
2. started eclipse as a regular user, installed CDT via eclipse's
update manager then stopped eclipse.
2. checked out and built eclim with eclipse.home and eclipse.local set
accordingly in my user.properties (the cdt feature was properly
recognized and compiled against with the latest eclim build script)
3. ran eclipse again as a regular user and I confirmed that the Eclim views
were available.
> >
> > It's also worth noting that the dead simple workaround is to just
> > download an eclipse distribution from
eclipse.org, untar it in your
> > home directory (no other steps necessary for installing eclipse), and
> > build eclim against that.
> >
> >
>
> I don't want to do that, I like using the package manager/software center.
> It is really starting to look like I'm going to need to, however.
I agree that it's ideal to have the system's package manager managing
your software as it should, but unfortunately eclipse's own software
management is grotesquely complex and mixing and matching between
using the system package manager and eclipse's can make matters worse.
So even though I dislike recommending it, installing from an
eclipse.org tar tends to provide the path of least resistance.
[1]
https://github.com/ervandew/eclim/commit/babc2b18f2a3c2033efbd55f95159376a6fad207
--
eric