| Sharing eclipse/plugins among several users [message #299778] |
Thu, 23 February 2006 16:37  |
Eclipse User |
|
|
|
Originally posted by: rob_dayton.yahoo.com
Hi,
What does it take for a group of users to share an eclipse installation
(separate copies?) Here's what I'm trying to do: I want all my users to be
using eclipse-3.1.2 with some plugins that I wrote. So I went ahead and
checked in the eclipse installation into perforce (our src management
tool) along with the plugins. The intent is that every user will check out
a copy of eclipse from the depot and use it in his workspace.
Couple of problems that I run into with this set up:
1. Everything works fine with my installation until I go ahead and do a
complete check-in as that makes all the files read-only. The next time I
want to use the install, it complains that a bunch of .fileTableLock files
do not have read access under eclipse-3.1.2/configuration
If I change the file permissions to be writeable, things work okay. Should
I be checking in these files at all? Or have some wrapper script that will
make these files writeable before the user can go ahead and run eclipse?
2. What about the launcher itself so the users can use the installation on
multiple environments? Should I be checking in two eclipse binaries, one
from the linux and one from the windows install and writing a script that
checks which platform the user is running on and pick the appropriate
launcher? I see in the Eclipse RCP book (Jeff McAffer) information on how
to export it to different platforms, how can I apply this to the basic
eclipse install itself?
Thanks,
Rob
|
|
|
| Re: Sharing eclipse/plugins among several users [message #299807 is a reply to message #299778] |
Fri, 24 February 2006 08:02  |
| Eclipse User |
|
|
|
Robert Dayton wrote:
> Couple of problems that I run into with this set up:
> 1. Everything works fine with my installation until I go ahead and do a
> complete check-in as that makes all the files read-only.
If you really want to do it this way, you would need to not check in the
configuration area generated files (like the lock files).
>
> 2. What about the launcher itself so the users can use the installation
> on multiple environments? Should I be checking in two eclipse binaries,
> one from the linux and one from the windows install and writing a script
> that checks which platform the user is running on and pick the
> appropriate launcher? I see in the Eclipse RCP book (Jeff McAffer)
> information on how to export it to different platforms, how can I apply
> this to the basic eclipse install itself?
What about another option. Make the eclipse-SDK*.zip and
eclipse-SDK*.tar.gz available. Have your users download and install it.
Then you don't have to worry about linux vs windows since the users
installed the correct version.
Then you have 2 options:
1) create an update site with your plugins (it's REALLY easy to do), and
have the users get them through the update manager ... I'd advise
downloading your plugins into a separate install location to keep the
main install clean.
2) you create a separate install location, add your plugins, and check
that into perforce. Each user has a local install of eclipse, checks
out the plugin install location into their workspace, and points eclipse
at it. Changes to your plugins are still controlled through perforce.
Later,
PW
|
|
|
Powered by
FUDForum. Page generated in 0.03714 seconds
Home