| Managing Plugins, Site-Wide [message #211143] |
Thu, 17 May 2007 20:54  |
Eclipse User |
|
|
|
Originally posted by: ian.tegebo.gmail.com
I'm trying to provide a uniform eclipse environment for my users. In
particular I want to be able to maintain plugins and configurations for
them so that they don't have to worry about adding update sites,
configuring common plugins, etc.
More specifically, I want to have the ruby development tools and radrails
setup and ready to go, perhaps also with subclipse. I can imagine the
list growing over time and fairly frequent updates/changes.
I'm running RHEL5 and expect to have approximately 10 users. Ideally I
would be able to update plugins from the command line so that I can
automate it for the whole group. I've found information about adding
product extension locations:
http://wiki.eclipse.org/index.php/FAQ_Can_I_install_plug-ins _outside_the_main_install_directory%3F
Encouraged, I then created such a directory and then copied over the RDT
and radrails features/plugins. To my dismay, there were a number of
dependencies that needed to be installed. I don't want to manually keep
track of these over time.
Is there a way to determine plugin dependencies in order to automate their
installation into my new product extension location?
|
|
|
| Re: Managing Plugins, Site-Wide [message #211169 is a reply to message #211143] |
Thu, 17 May 2007 21:39  |
| Eclipse User |
|
|
|
Originally posted by: news.pellaton.li
Hi
I keep a "clean" master installation that I carefully maintain. Our
sysadmins then create packages for the client distribution using this
master set-up. Some things are additionally done by scripts run during
the installation procedure (eg. per-user plug-in dirs in their $HOME,
shortcuts with appropriate params, ...).
However, the creation of the master installation is still a manual
process.
cu Michael
Ian Tegebo wrote:
> I'm trying to provide a uniform eclipse environment for my users. In
> particular I want to be able to maintain plugins and configurations for
> them so that they don't have to worry about adding update sites,
> configuring common plugins, etc.
>
> More specifically, I want to have the ruby development tools and
> radrails setup and ready to go, perhaps also with subclipse. I can
> imagine the list growing over time and fairly frequent updates/changes.
> I'm running RHEL5 and expect to have approximately 10 users. Ideally I
> would be able to update plugins from the command line so that I can
> automate it for the whole group. I've found information about adding
> product extension locations:
>
> http://wiki.eclipse.org/index.php/FAQ_Can_I_install_plug-ins _outside_the_main_install_directory%3F
>
>
> Encouraged, I then created such a directory and then copied over the RDT
> and radrails features/plugins. To my dismay, there were a number of
> dependencies that needed to be installed. I don't want to manually keep
> track of these over time.
>
> Is there a way to determine plugin dependencies in order to automate
> their installation into my new product extension location?
>
|
|
|
|
| Re: Managing Plugins, Site-Wide [message #211184 is a reply to message #211176] |
Fri, 18 May 2007 00:17 |
| Eclipse User |
|
|
|
Originally posted by: news.pellaton.li
> So do you manually keep track of plug-in dependencies in your master
> install?
Kind of - the master installation is done using the various update sites
of the different components we use. I did not yet have a case where the
a site could not offer all required dependencies automatically.
However, there are some plug-ins that re not available from an
update-site - usually they don't even have a feature, just plain
plug-ins. There the dependencies - if any - must be tracked manually.
cu Michael
|
|
|
| Re: Managing Plugins, Site-Wide [message #211321 is a reply to message #211143] |
Sat, 19 May 2007 04:42 |
| Eclipse User |
|
|
|
Originally posted by: murdoc_0.hotmail.com
Ian Tegebo wrote:
> I'm trying to provide a uniform eclipse environment for my users. In particular I want to be able to maintain plugins and configurations for them so that they don't have to worry about adding update sites, configuring common plugins, etc.
>
> More specifically, I want to have the ruby development tools and radrails setup and ready to go, perhaps also with subclipse. I can imagine the list growing over time and fairly frequent updates/changes.
> I'm running RHEL5 and expect to have approximately 10 users. Ideally I would be able to update plugins from the command line so that I can automate it for the whole group. I've found information about adding product extension locations:
>
> http://wiki.eclipse.org/index.php/FAQ_Can_I_install_plug-ins _outside_the_main_install_directory%3F
>
> Encouraged, I then created such a directory and then copied over the RDT and radrails features/plugins. To my dismay, there were a number of dependencies that needed to be installed. I don't want to manually keep track of these over time.
>
> Is there a way to determine plugin dependencies in order to automate their installation into my new product extension location?
How did you install the RDT/RadRails plugins outside of Eclipse? Most plug-ins come with in a .zip file that contains all the required dependencies. These can be extracted to the required folder.
I have the following eclipse environment, and have not used the Eclipse Update manager thingy for any of it. I manually upgrade versions of each plugin as I required it.
My eclipse environment is as follows (and yes, I do have RDT and RadRails installed):
/eclipse
/eclipse-plugins
/rdt
/eclispe
/features
/plugins
.eclipseextension
/radrails
/eclipse
/features
/plugins
.eclipseextension
.... etc
/eclipse-v3.2.2
/features
/links
/plugins
... etc
/eclipse-v3.3-M7
/features
/links
/plugins
... etc
The /links folder contains several .link files, which point the eclipse version to an additional directory to find a plugin. E.g.
rdt.link contains path= <path>/eclipse/eclipse-plugins/rdt
radrails.link contains path=<path>/eclipse/eclipse-plugins/radrails
This could be managed rather easily by putting the plugin files on a shared drive, and using a logon script to simply bulk-copy the required ..link files down to the user's installation. Using this method also makes it easy to 'blow away' an eclipse installation (for whatever reason), as the /links folder can simply be re-copied.
NOTE: As of RadRails v0.8, it is slightly more difficult to install, but it can be done.
--
|
|
|
Powered by
FUDForum. Page generated in 0.08564 seconds
] 
Search
Help
Register
Login
Home
