| Configuration.area and multiple eclipse instances [message #73054] |
Tue, 12 September 2006 18:17  |
Eclipse User |
|
|
|
Originally posted by: eclipse-dev.volanakis.de
Hi there,
I am trying to understand how well multiple running eclipse instances
will work with a common configuration.area. The documentation on Eclipse
multi-user installs [a] did not answer my questions fully, since the
scenarios explained below do not directly apply.
What I would like to know is, if the following scenarios are supported
by Eclipse 3.1 or later:
1. In this scenario a set of developers shares one user-account: we have
one eclipse installation, one set of plugins, using the same
configuration area, with many eclipse instances running concurrently.
How well is this supported by the current implementation? What is the
risk of side-effects, considering that one developer might choose to
modify the configuration through the update manager while other eclipse
instances are running?
2. In this scenario we have multiple eclipse-installations (based on the
same platform release) with different sets of plugins in each
installation. All installations are configured to use the same
configuration area (before this is dismissed as exotic consider this:
each installation is a "shared install" with the default configuration
area being read-only, so that $HOME/.eclipse/org.eclipse.platform_3.1.1/
is the configuration area used in each case). Could this cause trouble?
Thanks for your input.
Kind regards,
Elias.
[a]
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse. platform.doc.isv/reference/misc/multi_user_installs.html
|
|
|
| Re: Configuration.area and multiple eclipse instances [message #73252 is a reply to message #73054] |
Tue, 19 September 2006 12:34  |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer.REMOVE.ca.ibm.com
Elias Volanakis wrote:
> 1. In this scenario a set of developers shares one user-account: we have
> one eclipse installation, one set of plugins, using the same
> configuration area, with many eclipse instances running concurrently.
> How well is this supported by the current implementation? What is the
> risk of side-effects, considering that one developer might choose to
> modify the configuration through the update manager while other eclipse
> instances are running?
The typical use of multiple users/instances sharing the same
configuration involves the configuration being locked and only managed
or manipulated by one person/configuration. Update manager and several
other plugins have explicit support for managing changes to their
configuration data but this is on a case by case basis. That is, there
is nothing that we can do on a global scale to insulate plugins from
changing configurations so your mileage may vary.
> 2. In this scenario we have multiple eclipse-installations (based on the
> same platform release) with different sets of plugins in each
> installation. All installations are configured to use the same
> configuration area (before this is dismissed as exotic consider this:
> each installation is a "shared install" with the default configuration
> area being read-only, so that $HOME/.eclipse/org.eclipse.platform_3.1.1/
> is the configuration area used in each case). Could this cause trouble?
First a clarification. What exactly do you mean by "multiple installs"?
If there is one shared configuration area then you really only have
one install (as pointed to by the shared configuration area). You would
then in fact have multiple configurations each parented by the shared
install. This setup is possible and designed for though likely somewhat
off the normal path so there may be issues. I have seen people doing it
with apparent success.
Jeff
|
|
|
Powered by
FUDForum. Page generated in 0.02755 seconds
] 
Search
Help
Register
Login
Home
