Re: [platform-update-dev] plugin paths

[cisco@xxxxxxxxxx]

Actually this has nothing specifically to do with Linux.  It's the concept of minimizing the number of Eclipse instances installed on the user's system.  The article you reference doesn't address this.  It aggravates it by specifying that I should place my eclipse directory under a product specific directory name (\cool\eclipse\...), which implies that distinct products cannot share an Eclipse base install.

/-----------
|   Steve Francisco
|   cisco@xxxxxxxxxx
|   WebSphere Studio Application Developer
|   Linux Port Team Lead
\-----------

John Kellerman/Raleigh/IBM@IBMUS Sent by: platform-update-dev-admin@xxxxxxxxxxx 12/06/2001 01:39 PM Please respond to platform-update-dev

To:        platform-update-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-update-dev] plugin paths

Note that while plugin path works you need to consider that, in addition to worrying about managing your environment, this parameter is not intended to be supported as a command line parameter for tools built on eclipse.  It looks like you're attempting to use this as way of solving some installation requirements you have in Linux.  In general, take a look at the branding/packaging guide at http://www.eclipse.org/articles/product-guide/guide.html.  If this doesn't solve your requirement, I'd suggest a discussion on the newsgroup.

John Kellerman
Product Manager, WebSphere Studio Workbench
OTI - Research Triangle Park, NC
kellrman@xxxxxxxxxx

Please respond to platform-update-dev@xxxxxxxxxxx

Sent by:        platform-update-dev-admin@xxxxxxxxxxx

To:        platform-update-dev@xxxxxxxxxxx
cc:        
Subject:        Re: [platform-update-dev] plugin paths



The plugin-path support works in 1.0 and will continue to work in 2.0 .... but using it basically puts you in a condition of being responsible for controlling your environment. So, for example, depending on what you do, you may not pickup any updates done by the update manager (eg. if your plugin path is not updated to reflect the change).

Please respond to platform-update-dev@xxxxxxxxxxx

Sent by:        platform-update-dev-admin@xxxxxxxxxxx

To:        platform-update-dev@xxxxxxxxxxx
cc:        
Subject:        [platform-update-dev] plugin paths



Is the use of the -plugins parameter advisable in Eclipse v1?  We are building a product on it and it would make a lot of sense to have separate installs of eclipse itself, and various subcomponents.  Without this we would end up with each product installing its own copy of the workbench code.  From my initial tests is seems to work properly, but since there is a lack of documentation I wanted to find out what the official recommendation is.

-- Steve Francisco