Thanks for the notes. Its not exactly what we're looking for. I need a
way to create and maintain our development environment for our team. We
currently use our version control system and that system requires
version control commands to delete files. We currently put each plugin
in its own directory. That makes it easy to delete a plugin from our
version control system. We've thought about using a shared pulse
profile but they aren't "ready to rock" with Eclipse 3.4.
Our real requirement is that we be able to centrally create and manage
an eclipse install package that can be copied to developer's machines. I
guess we could create some kind of "gold master" copy on a shared
drive and right protected and then have everyone copy it to their
machines but it seems simpler to manage this in perforce. For the time
being, we are looking at using the scripts provided in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=224908 . They let us
convert 3.4 back to the 3.3 update manager with its support of external
directories for plugins.