I'm migrating our Eclipse release from 3.3 -> 3.4, and although I've
scoured the wiki, I can't find out how to make multi-user installs work
in the new world.
A couple of things I used to do:
1) We build an Eclipse release from the base platform + CDT + our own
plugins. We build CDT + plugins locally and install them centrally for
our developers to use. Our product is versioned, with users able to
choose which version to run via a wrapper shell script. We also provide
versions of net plugins wrapped as Eclipse extensions. The layout is
something like:
eclipse/
3.3-1/
eclipse
...
3.3-2/
eclipse
...
...
pydev_x_y_z
.eclipseextension
...
clearcase_x_y_z
...
...
This allowed users to choose a version of the base platform + other
features as they see fit. In general we don't want plugins stored per
user for disk space reasons, and the ability to diagnose and
troubleshoot problems against a known set of plugins is invaluable.
(Although if advanced users have a local extension location, then that's
fine too...)
2) The other thing we do is apply very small patches to the platform
(such as https://bugs.eclipse.org/bugs/show_bug.cgi?id=86973) which
requires patching only a couple plugins. In 3.3 I did this by exporting
the plugin from my PDE workspace, drop it in the plugins folder of a new
product release, and tweak the feature.xml appropriately. While
certainly hacky, this is much easier than building all of the platform...
How do I do this in 3.4?
It's likely I've somehow missed the page which says how to handle these
issues. I'd be very grateful if someone could point me in the right
direction!