| Separate Eclipse and Plugins Installation Issue [message #65941] |
Wed, 18 May 2005 17:24  |
Eclipse User |
|
|
|
Originally posted by: adalbert.perbandt.infineon.com
Hi there,
I'm fiddling 'round with a somewhat complex eclipse (3.1M7) installation
and would like to get some advice to do it right. The situation is as
follows:
Eclipse will be used for several purposes in my environment. Some people
use the EPIC plugin for doing Perl development. Others want to use the CDT
plugin for their C/C++ development. Some will work with the ClearCase
config management system by IBM Rational) and -- last but not least --
some developers will do Java development with Eclipse.
1. issue: I learned that it is possible to setup eclipse in a way that one
only installs the platform in one place and install the plugins, each
separate from the others, in a different place. Then the eclipse users
would configure "their" eclipse according to their needs, e.g. the C++
developers would define an extension point for the C++ plugin, the Java
folks would extend their eclipse with a JDT extension point, etc.
The installation directory structure for this scenario looks like this:
Eclipse Platform Installation:
/opt/eclipse_3.1/eclipse-platform-3.1M7-solaris-motif/eclips e
Plugins Installation:
/opt/eclipse-plugins/CDT/eclipse
/JDT/eclipse
/ccase/eclipse
[...]
All the "eclipse" directories of the installed plugins contain a file
".eclipseextension" which makes the respective directory usable as an
extension point.
The question here is: Does it really make sense to split off an eclipse
installation that way? Some colleagues meant this would make eclipse start
significantly faster. Is this true?
2. I'd prefer to have an eclipse installation with all needed plugins
available when eclipse is started (without any per user configuration of
extension points necessary). But still I'd like to have the plugins
installed in the way shown above, to be able to add new ones or perform
updates for plugins without the update manager by simply replacing the
contents of a plugin's "eclipse" directory. I learned that one can create
a directory "links" inside the "eclipse" directory inside the base eclipse
installation and put a file .link into it which contains a statement like
this:
path=/opt/eclipse-plugins
Then all plugins would have to be installed together in a directory
"/opt/eclipse-plugins/eclipse". Would it be possible to have for each
plugin a separate "eclipse" directory, as shown in the plugin installation
directory given for issue 1?
Thanks in advance for any helpful hint
Regards
Adalbert Perbandt
|
|
|
| Re: Separate Eclipse and Plugins Installation Issue [message #65971 is a reply to message #65941] |
Wed, 18 May 2005 18:52  |
| Eclipse User |
|
|
|
Originally posted by: tominospam-eclipse.yahoo.com
Hi Adalbert
I believe it makes sense to split the plugins form the eclipse installation.
The developers can install the plugins with the update manager of
Eclipse. To do this go to "Help > Software Updates > Find and
Install..." a dialog will appear and you choose "Search for new features
to install". You'll get a new dialog and there you choose "New local
site...". Point to the plugin, for example CDT and install it.
To disable or uninstall a plugin, use "Help > Software Updates > Manage
Configuration..."
Actually it's not correct to talk about plugins, since these are
features we're talking about. As far as I know, you can only install and
manage features the way I described.
Hope this will help.
Best regards,
Tomi
Adalbert Perbandt wrote:
> Hi there,
>
> I'm fiddling 'round with a somewhat complex eclipse (3.1M7) installation
> and would like to get some advice to do it right. The situation is as
> follows:
>
> Eclipse will be used for several purposes in my environment. Some people
> use the EPIC plugin for doing Perl development. Others want to use the
> CDT plugin for their C/C++ development. Some will work with the
> ClearCase config management system by IBM Rational) and -- last but not
> least -- some developers will do Java development with Eclipse.
>
> 1. issue: I learned that it is possible to setup eclipse in a way that
> one only installs the platform in one place and install the plugins,
> each separate from the others, in a different place. Then the eclipse
> users would configure "their" eclipse according to their needs, e.g. the
> C++ developers would define an extension point for the C++ plugin, the
> Java folks would extend their eclipse with a JDT extension point, etc.
>
> The installation directory structure for this scenario looks like this:
>
> Eclipse Platform Installation:
>
> /opt/eclipse_3.1/eclipse-platform-3.1M7-solaris-motif/eclips e
>
> Plugins Installation:
>
> /opt/eclipse-plugins/CDT/eclipse
> /JDT/eclipse
> /ccase/eclipse
> [...]
>
> All the "eclipse" directories of the installed plugins contain a file
> ".eclipseextension" which makes the respective directory usable as an
> extension point.
>
> The question here is: Does it really make sense to split off an eclipse
> installation that way? Some colleagues meant this would make eclipse
> start significantly faster. Is this true?
>
> 2. I'd prefer to have an eclipse installation with all needed plugins
> available when eclipse is started (without any per user configuration of
> extension points necessary). But still I'd like to have the plugins
> installed in the way shown above, to be able to add new ones or perform
> updates for plugins without the update manager by simply replacing the
> contents of a plugin's "eclipse" directory. I learned that one can
> create a directory "links" inside the "eclipse" directory inside the
> base eclipse installation and put a file .link into it which contains a
> statement like this:
>
> path=/opt/eclipse-plugins
>
> Then all plugins would have to be installed together in a directory
> "/opt/eclipse-plugins/eclipse". Would it be possible to have for each
> plugin a separate "eclipse" directory, as shown in the plugin
> installation directory given for issue 1?
>
> Thanks in advance for any helpful hint
>
> Regards
>
> Adalbert Perbandt
>
|
|
|
| Re: Separate Eclipse and Plugins Installation Issue [message #66454 is a reply to message #65971] |
Thu, 19 May 2005 09:37 |
| Eclipse User |
|
|
|
Originally posted by: adalbert.perbandt.infineon.com
Tomi Schuetz wrote:
> Hi Adalbert
> I believe it makes sense to split the plugins from the eclipse installation.
> The developers can install the plugins with the update manager of
> Eclipse. To do this go to "Help > Software Updates > Find and
> Install..." a dialog will appear and you choose "Search for new features
> to install". You'll get a new dialog and there you choose "New local
> site...". Point to the plugin, for example CDT and install it.
Correct me if I'm wrong but my understanding of the procedure you describe
is that each eclipse user would have to install updates for his own
eclipse installation?
Our software installation model is that we have software installed on file
systems which are readonly mounted for the users. So an eclipse user will
not be able to update the eclipse installation. He will not have his own
eclipse install but use one centrally provided and maintained eclipse
installation.
What I meant with splitting the plugins/features from the eclipse
installation was that I'd like to have a different (but central) location
where all the eclipse features are installed AND each user would have to
configure eclipse through the extension point mechanism to contain just
those features he needs. The question is if this would bring any
performance gain during startup of eclipse or eclipse usage compared to a
"fat" eclipse installation with all available features put together.
> Actually it's not correct to talk about plugins, since these are
> features we're talking about. As far as I know, you can only install and
> manage features the way I described.
O.k. understand.
Thanks and regards
Adalbert Perbandt.
|
|
|
| SOLVED PARTLY: Re: Separate Eclipse and Plugins Installation Issue [message #67053 is a reply to message #65941] |
Fri, 20 May 2005 13:39 |
| Eclipse User |
|
|
|
Originally posted by: adalbert.perbandt.infineon.com
Hi there,
I found a nice solution for the 2nd part of the problem.
> The installation directory structure looks like this:
> Eclipse Platform Installation:
> /opt/eclipse_3.1/eclipse-platform-3.1M7-solaris-motif/eclips e
> Plugins Installation:
> /opt/eclipse-plugins/CDT/eclipse
> /JDT/eclipse
> /ccase/eclipse
> [...]
In the directory
/opt/eclipse_3.1/eclipse-platform-3.1M7-solaris-motif/eclips e/links
I created not just one but a couple of files named
link.CDT
link.JDT
link.ccase
with this one liner inside:
path=/opt/eclipse-plugins/CDT
(example for the CDT plugin).
The result of this setup is that the eclipse installation obviously treats
the specification inside the ".link.something" file as the definition of
an extension point. This way I have each plugin/feature installed
separately from the others and can freely modify/add/remove each single
plugin/feature.
I hope that this trick is not working based on some undocumented side
effects.
Any comments on this are welcome.
Regards
Adalbert Perbandt.
|
|
|
Powered by
FUDForum. Page generated in 0.07619 seconds
] 
Search
Help
Register
Login
Home
