[platform-releng-dev] (no subject)

[Andrew_Cornwall@xxxxxxx]

>This is probably not targeted correctly, as I could not find an answer
>anywhere in  this newsgroup or the eclipse site.  How should an
>installation process discover where Eclipse installations are located,
>in order to deploy my plugin to them after they have been installed?
>Or, is this a situation where there is no "eclipse-native" installation
>location device, that it's dependent upon whomever redistributes?

You're not the only one to wonder about install issues... I think the 
platform-releng-dev@xxxxxxxxxxx mailing list is the right place for such 
matters.

I've come up with a proposal that hasn't been adopted (or even discussed) 
yet... join the mailing list and maybe we can start a new standard :-)

Proposal for Eclipse Installation Standard - by Andrew Cornwall
=====================================================

Multiple vendors are providing plugins for Eclipse technology. In
addition, more than one vendor is shipping the entire Eclipse
framework. Because these different vendors sometimes change the
directory structure for Eclipse, everyone's install utility has to
take these differences into account. This results in a combinatorial
explosion for writers of install programs.

In order to reduce this, we offer the following suggestion:

1. All providers of the Eclipse framework include, in the base
directory of their installation, a text file with the name plugin.inf
with the following format:

BrandName <my branding name>
BrandVersion <my branding version>
EclipseVersion <my Eclipse version>
PluginDir <my plugin dir>

Each keyword is case sensitive. The value for a keyword is a text
string corresponding to all the text after the first space up to the
end-of-line. (For instance, in "BrandingName Foo", the value is
"Foo".) Newline and other control characters are forbidden. Text
values must not be more than 55 characters long.

The meaning of each keyword is explained below.

BrandName: this is the name that the Eclipse platform was
installed under. For instance, WSDD might have:
    BrandName WebSphere Studio Device Developer

BrandVersion: this is the version that the Eclipse platform was
installed as. For instance, WSDD might have:
    BrandVersion 4.03

Note that BrandName and BrandVersion must not be used for anything
except display, as-is, to the user.

For instance, an install program might ask "Do you want to install
the new plugin in the WebSphere Studio Device Developer 4.03
directory?". However, it is forbidden from changing the install based
on internal computations with BrandName and BrandVersion.)

EclipseVersion: this is the name of the underlying Eclipse technology
(as specified by the Eclipse team). Platform providers are not
permitted to modify this field. Programs *may* use this field to
determine if the Eclipse platform is compatible with their plugin.
An instance of EclipseVersion might be:
   EclipseVersion: 1.0

PluginDir: this specifies where on the filesystem the Eclipse plugin
directory is located, relative to the installed location. For
instance, because the plugin directory for WSDD is located off of the
base install directory, its value will be:
    PluginDir plugin

If another platform chose to have the following directory structure:
MyPlatform
  Eclipse
    plugins

then its PluginDir should be:
    PluginDir Eclipse/plugins
if it is Unix-based, or
    PluginDir Eclipse\plugins
if it is Windows-based.

(Note that plugin.inf will be located in the MyPlatform directory,
because that is the base install directory.)

The PluginDir is operating-system specific, but must maintain case
for the directories it names. There is no trailing slash or backslash
permitted when specifying the plugin directory. Accessing the parent
or current directory
  (PluginDir Eclipse/../../MyPlatform/./Eclipse/plugins)
is forbidden.

2. If the user chooses to install the plugins (rather than installing
an entire copy of the Eclipse platform), the install program may
search the entire file system, or part of the file system (such as
/home/<user>), for plugin.inf files. These files may be presented
these to the user as potential places to install the plugins.
If the user chooses to install to a location, the plugin files are
copied to subdirectories of the PluginDir for that installation. It
is recommended that the installation program display to the user the
directory the plugin.inf file was found (the base install dir) as
well as the BaseName and BaseVersion.

If the install program finds plugin.inf files in a directory X and a
subdirectory of X, then the subdirectory must be ignored, and X
itself must be the only location presented as an install option to
the user.

        Andrew Jr.
======================================================================
Object Technology Inc. Technical Support        phone:  (602) 569-3322
11811 North Tatum Boulevard, Suite 2400           fax:  (602) 569-6300
Phoenix, Arizona, USA  85028-1614              e-mail: support@xxxxxxx
OTI is a wholly owned subsidiary of IBM Canada, Ltd.