platform-update-home/doc/eclipse_update_packaging.html

Parent Directory | Revision Log | Patch

-revision 1.10, Mon Dec  9 18:52:19 2002 UTC
+revision 1.11, Thu Jan  2 14:05:51 2003 UTC
 Line 21
  <p><b>Change History:</b> </p>
  <ul>
-     <li><small>2.0.15<br>
+      <li><small>2.0.16</small>     <small><br>
       </small>
      <ul>
-       <li><small>added &lt;site&gt;&lt;feature&gt; os,arch,nl,ws,patch tag</small><br>
+       <li><small>added &lt;site&gt;&lt;feature&gt; os,arch,nl,ws support
+ "*"</small></li>
+     </ul>
         </li>
+   <li><small>2.0.15</small>
+     <ul>
+       <li><small>added &lt;site&gt;&lt;feature&gt; os,arch,nl,ws,patch tag</small></li>
      </ul>
     </li>
    <li><small>2.0.14<br>
-Line 73
+Line 78
    <ul>
     <li> <font size="-1">&lt;site&gt; &lt;feature&gt; changes - additional
- markup to optionally expose feature identification information to speed up
+  markup to optionally expose feature identification information to speed
- searches</font></li>
+ up  searches</font></li>
      <li> <font size="-1">removed obsolete text</font></li>
      <li> <font size="-1">web-triggered update not in 2.0</font></li>
      <li> <font size="-1">no assist in 2.0 for license/ "key file" handling
-Line 165
+Line 170
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Controlling_Access">Controlling
   Access</a>  <br>
    <a href="#Eclipse_Install">Eclipse Install</a>  <br>
-   &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Default_Install_Layout">Default
+    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-  Install Layout</a>  <br>
+  href="#Default_Install_Layout">Default   Install Layout</a>  <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="#Unmanaged_Plugins">"Unmanaged"
   Plug-Ins</a>  <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
-Line 189
+Line 194
   R2.0 supplies a default concrete implementation of this framework. <li>
      <b>  feature support</b></li>
      <br>
-   In R2.0 the concept of a <i>component</i> and <i>configuration</i> is merged
+    In R2.0 the concept of a <i>component</i> and <i>configuration</i> is
-  into <i>feature</i>. Features define the packaging structure for a group
+ merged  into <i>feature</i>. Features define the packaging structure for
- of related plug-ins, plug-in fragments, and optionally non-plug-in files.
+ a group of related plug-ins, plug-in fragments, and optionally non-plug-in
- Features are treated purely as an installation and packaging construct. They
+ files. Features are treated purely as an installation and packaging construct.
- do not play a role during Eclipse plug-in execution. Features do not nest.
+ They do not play a role during Eclipse plug-in execution. Features do not
- They are simply an inclusive "manifest" of the plug-ins, fragments and other
+ nest. They are simply an inclusive "manifest" of the plug-ins, fragments
- files that make up that feature. If features are logically made up of plug-ins
+ and other files that make up that feature. If features are logically made
- from "sub-features", the top-level feature "manifest" must be fully resolved
+ up of plug-ins from "sub-features", the top-level feature "manifest" must
- at packaging time. <li> <b>default feature archive format</b></li>
+ be fully resolved at packaging time. <li> <b>default feature archive format</b></li>
      <br>
    R1.0 components were packaged as a single Java .jar containing the component
   manifest as well as the actual plug-in files. The problem with this approach
-Line 210
+Line 215
    Default Eclipse update server must contain a <i>site map</i> file (site.xml).
   This is an evolution of the R1.0 install.index support. The rationale for
   using a structured site defined by the map rather than a "free form" web
- site, is the ability to present a consistent installation experience for the
+  site, is the ability to present a consistent installation experience for
- user. Also, this provides the necessary structure for discovery of available
+ the user. Also, this provides the necessary structure for discovery of available
  updates. Additional support for "free form" browsing may be considered in
  future work.    <li> <b>using native install/ uninstall</b></li>
      <br>
-   The primary mechanism for installing and updating Eclipse features is the
+    The primary mechanism for installing and updating Eclipse features is
-  built-in installation and update support. Some products may instead choose
+ the  built-in installation and update support. Some products may instead
-  to use native installer technology (eg. MSI, RPM, etc) to deliver Eclipse
+ choose  to use native installer technology (eg. MSI, RPM, etc) to deliver
-  features. However, native installers do not implement the required support
+ Eclipse  features. However, native installers do not implement the required
-  for understanding the Eclipse installation structure. In particular, the
+ support  for understanding the Eclipse installation structure. In particular,
- native uninstallers will, by default, remove plug-in files that were installed
+ the native uninstallers will, by default, remove plug-in files that were
- using the native installer without regard to these plug-ins being needed
+ installed using the native installer without regard to these plug-ins being
- by other features. As a result, features installed using native installers
+ needed by other features. As a result, features installed using native installers
  must be written into private product-specific installation location and not
  the shared Eclipse installation location. The shared Eclipse is made aware
  of the produce-specific location via an installed "link file". <li> <b>custom
  install handling</b></li>
      <br>
    In many cases the standard installation handling supplied by Eclipse is
- not be sufficient to handle various custom requirements. To accommodate this,
+  not be sufficient to handle various custom requirements. To accommodate
-  R2.0 Eclipse supports custom install handlers packaged as part of the feature
+ this,  R2.0 Eclipse supports custom install handlers packaged as part of
-  and executed during the feature installation. <li> <b>path naming conventions</b></li>
+ the feature  and executed during the feature installation. <li> <b>path naming
+ conventions</b></li>
      <br>
    R1.0 mandated the use of the various identifiers and versions inside the
   packaged archives (eg. directory path names for plug-ins). This approach
-Line 246
+Line 252
  <h3> <a name="Concepts"></a> Concepts</h3>
     <b>Plug-in</b> <br>
    Eclipse developers build plug-ins. Plug-ins are the base units of execution
-  recognized by the Eclipse runtime environment. In general, plug-ins are not
+   recognized by the Eclipse runtime environment. In general, plug-ins are
- exposed to users that select function during installation or update. The
+ not exposed to users that select function during installation or update.
- reason is that plug-in boundaries are established by developers for development
+ The reason is that plug-in boundaries are established by developers for development
   reasons (like function reuse) and present the wrong level of granularity
  in terms of what the user sees as the unit of function.
  <p>While plug-ins are being developed (ie. are frequently being changed),
-Line 256
+Line 262
   This will generally depend on the particular development tool being used.
   Typically, however, the developer will likely setup the plug-in to execute
   from a directory tree containing exposed .class files, rather than executing
-  from a .jar (requires an extra step to create the .jar and we all know developers
+   from a .jar (requires an extra step to create the .jar and we all know
-  hate extra steps). Also, at this stage the developer does not pay particular
+ developers  hate extra steps). Also, at this stage the developer does not
-  attention to plug-in versioning information, because the plug-in is continually
+ pay particular  attention to plug-in versioning information, because the
-  changing. </p>
+ plug-in is continually  changing. </p>
  <p>However, when the plug-in is ready to be packaged, it needs to be converted
   to a form suitable for packaging and installation. Typically it means creation
-  of the runtime .jar(s) and removing any development-time files (source, exposed
+   of the runtime .jar(s) and removing any development-time files (source,
- .class files, etc). It also means updating the plugin.xml manifest with the
+ exposed .class files, etc). It also means updating the plugin.xml manifest
- formal plug-in version and reflecting the version in the plug-in directory
+ with the formal plug-in version and reflecting the version in the plug-in
- name (see "Concurrent Plug-In Version Support" for details). </p>
+ directory name (see "Concurrent Plug-In Version Support" for details). </p>
  <p><b>Plug-in Fragment</b> <br>
    Plug-in Fragments (or simply Fragments) allow independent packaging of
  certain  aspects of the base plug-in. This includes (but may not be limited
  to) translated  resources for the plug-in, OS-specific or windowing-system-specific
- code.  At runtime, fragments are logically merged into the base plug-in.
+ code.  At runtime, fragments are logically merged into the base plug-in. From
- From a packaging point of view, the install and update support does not really
+ a packaging point of view, the install and update support does not really
  differentiate  between plug-ins and their related fragments. </p>
  <p><b>Feature</b> <br>
    A feature is an installation packaging mechanism used to define a group
  of versioned plug-ins and/or plug-in fragments plus non-plug-in files that
- is used to deliver some user function. A feature can also include other features.
+  is used to deliver some user function. A feature can also include other
-  Features are exposed to users as part of the packaging and installation
+ features.  Features are exposed to users as part of the packaging and installation
  process,  because they represent a unit of function selection. Features also
  represent  a unit of installation. Features carry a version identifier.</p>
  <p>Features are packaged as a feature archive, referencing the required plug-ins,
   plug-in fragments and optional non-plug-in files. The feature archives are
-  placed on an update server for download and installation by the Eclipse
+  placed on an update server for download and installation by the Eclipse update
- update  manager, or they can be used as the input into a formal packaging
+  manager, or they can be used as the input into a formal packaging process
- process  using one of the "traditional" installer technologies. The format
+  using one of the "traditional" installer technologies. The format of the
- of the feature archive is described later. </p>
+ feature archive is described later. </p>
  <h3> <a name="Framework"></a> Framework</h3>
     The 2.0 installation and update support is provided as a framework that
-Line 299
+Line 305
     <li> concrete implementations of feature (IFeature interface) that can
  be used to support alternate packaging schemes. New concrete feature types
  are  registere via the "org.eclipse.update.featureTypes" extension point.</li>
-     <li> concrete implementations of site (ISite interface) that can be used
+      <li> concrete implementations of site (ISite interface) that can be
-  to support alternate site layout, or site behavior. New concrete site types
+ used  to support alternate site layout, or site behavior. New concrete site
-  are registered via the "org.eclipse.update.siteTypes" extension point.</li>
+ types   are registered via the "org.eclipse.update.siteTypes" extension point.</li>
      <li> each feature can specify a custom install handler as part of its
  feature  manifest. Install handlers (IInstallHandler interface) are dynamically
  invoked as part of the installation process to handle non-plugin data, plus
-Line 316
+Line 322
        <tr>
     <td><b>Note: <i>The reminder of this document describes the default concrete
   implementation of the framework delivered with Eclipse. It specifies the
- structure of the default feature implementation, as well as the default site
+  structure of the default feature implementation, as well as the default
- implementation, plus the corresponding xml files (feature.xml and site.xml).
+ site  implementation, plus the corresponding xml files (feature.xml and site.xml).
  Providers of alternate concrete implementations can extend&nbsp; parts or
  all of the default Eclipse implementation. This includes providing a mechanism
  for dynamic computation of the site map (site.xml)</i></b></td>
-Line 341
+Line 347
  <h3> <a name="Feature_Archive"></a> Feature Archive</h3>
     The feature packaging information is placed into a separate Java .jar.
- Standard Java jar facilities are used for constructing feature archives. Feature
+  Standard Java jar facilities are used for constructing feature archives.
- archives reference separately packaged plug-in archives (see next section)
+ Feature archives reference separately packaged plug-in archives (see next
- and non-plug-in files.
+ section) and non-plug-in files.
  <p>Features are identified using a structured identifier based on the provider
-  internet domain name. For example, organization eclipse.org may produce feature
+   internet domain name. For example, organization eclipse.org may produce
- org.eclipse.javatooling. The character set used for feature identifiers is
+ feature org.eclipse.javatooling. The character set used for feature identifiers
- as specified for plug-in identifiers (see reference information describing
+ is as specified for plug-in identifiers (see reference information describing
   the plug-in manifest). </p>
  <p>The recommended convention for naming the feature archives is <br>
-Line 378
+Line 384
  <p><tt>&lt;?xml encoding="ISO-8859-1"?&gt;</tt> </p>
- <p><tt>&lt;!ELEMENT feature (install-handler?, description?, copyright?, license?,
+ <p><tt>&lt;!ELEMENT feature (install-handler?, description?, copyright?,
- url?, includes*, requires?, plugin*, data*)&gt;</tt> <br>
+ license?, url?, includes*, requires?, plugin*, data*)&gt;</tt> <br>
    <tt>&lt;!ATTLIST feature</tt> <br>
    <tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
   CDATA #REQUIRED</tt> <br>
-Line 461
+Line 467
    <tt>&nbsp;&nbsp;&nbsp; optional &nbsp;&nbsp;&nbsp;&nbsp; </tt><tt>&nbsp;&nbsp;&nbsp;
   (true | false) "false"</tt><tt>&nbsp;<br>
    </tt><tt>&nbsp;&nbsp;&nbsp; match&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-  &nbsp;&nbsp;&nbsp; (perfect | equivalent | compatible | greaterOrEqual) "compatible"</tt><tt>
+   &nbsp;&nbsp;&nbsp; (perfect | equivalent | compatible | greaterOrEqual)
- &nbsp; &nbsp;&nbsp;&nbsp; </tt><br>
+ "compatible"</tt><tt> &nbsp; &nbsp;&nbsp;&nbsp; </tt><br>
    <tt>&nbsp;&nbsp;&nbsp; search_location&nbsp;&nbsp; </tt><tt>(</tt><font
   color="#000000"><tt> root | self | both) "root"</tt></font><br>
    <tt>&gt;</tt> </p>
-Line 489
+Line 495
   CDATA #REQUIRED</tt> <br>
    <tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
   #REQUIRED</tt> <br>
-   <tt>&nbsp;&nbsp;&nbsp; fragment&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true | false)
+    <tt>&nbsp;&nbsp;&nbsp; fragment&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true |
-  "false"</tt> <br>
+ false)  "false"</tt> <br>
    <tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
   CDATA #IMPLIED</tt> <br>
    <tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Line 536
+Line 542
  list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
   . Indicates this feature should only be installed on one of the specified
   os systems. If this attribute is not specified, the feature can be installed
-  on all systems (portable implementation). This information is used as a hint
+   on all systems (portable implementation). This information is used as a
- by the installation and update support (user can force installation of feature
+ hint by the installation and update support (user can force installation
- regardless of this setting).</li>
+ of feature regardless of this setting).</li>
      <li> arch - optional machine architecture specification. A comma-separated
   list of architecture designators defined by Eclipse (see Javadoc for <tt>
   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
-Line 550
+Line 556
  list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
   . Indicates this feature should only be installed on one of the specified
   ws systems. If this attribute is not specified, the feature can be installed
-  on all systems (portable implementation). This information is used as a hint
+   on all systems (portable implementation). This information is used as a
- by the installation and update support (user can force installation of feature
+ hint by the installation and update support (user can force installation
- regardless of this setting).</li>
+ of feature regardless of this setting).</li>
      <li> nl - optional locale specification. A comma-separated list of locale
   designators defined by Java. Indicates this feature should only be installed
   on a system running with a compatible locale (using Java locale-matching
- rules). If this attribute is not specified, the feature can be installed
+ rules). If this attribute is not specified, the feature can be installed on
- on all systems (language-neutral implementation). This information is used
+ all systems (language-neutral implementation). This information is used as
- as a hint by the installation and update support (user can force installation
+ a hint by the installation and update support (user can force installation
  of feature regardless of this setting).</li>
      <li> colocation-affinity - optional reference to another feature identifier
-  used to select the default installation location for this feature. When this
+   used to select the default installation location for this feature. When
- feature is being installed as a new feature (no other versions of it are
+ this feature is being installed as a new feature (no other versions of it
- installed), an attempt is made to install this feature in the same installation
+ are installed), an attempt is made to install this feature in the same installation
   location as the referenced feature.</li>
      <li> primary - optional indication specifying whether this feature can
   be used as a <a href="#Dominant_Feature">primary feature</a> . Default if
-Line 581
+Line 587
     <li> library - optional .jar library containing the install handler classes.
   If specified, the referenced .jar must be contained in the feature archive.
   It is specified as a path within the feature archive, relative to the feature.xml
-  entry. If not specified, the feature archive itself is used to load the install
+   entry. If not specified, the feature archive itself is used to load the
- handler classes. This attribute is only interpreted if <i>class</i> attribute
+ install handler classes. This attribute is only interpreted if <i>class</i>
- is also specified</li>
+ attribute is also specified</li>
      <li> handler - optional identifier of the install handler. The value
  is  interpreted depending on the value of the <i>library</i> attribute. If
-       <i>  library</i> is specified,&nbsp; the value is interpreted as a
+       <i>  library</i> is specified,&nbsp; the value is interpreted as a fully
- fully qualified  name of a class contained in the specified <i>library</i>.
+ qualified  name of a class contained in the specified <i>library</i>. If
- If <i>library</i>   is not specified, the value is is interpreted as an extension
+       <i>library</i>   is not specified, the value is is interpreted as an
- identifier  of an extension registered in the <i>org.eclipse.update.installHandlers</i>
+ extension identifier  of an extension registered in the <i>org.eclipse.update.installHandlers</i>
    extension point. In either case, the resulting class must implement the
-       <i> IInstallHandler</i> interface. The class is dynamically loaded and
+        <i> IInstallHandler</i> interface. The class is dynamically loaded
- called at specific points during feature processing. The handler has visibility
+ and called at specific points during feature processing. The handler has
- to the API classes from the update plug-in, and Eclipse plug-ins required
+ visibility to the API classes from the update plug-in, and Eclipse plug-ins
- by the update plugin.</li>
+ required by the update plugin.</li>
    </ul>
      <li> &lt;description&gt; - brief component description as simple text.
-Line 608
+Line 614
  each national language.</li>
    </ul>
-     <li> &lt;copyright&gt; - feature copyright as simple text. Intended to
+      <li> &lt;copyright&gt; - feature copyright as simple text. Intended
-  be translated.</li>
+ to  be translated.</li>
    <ul>
     <li> url - optional URL for the full description as HTML. The URL can
-Line 623
+Line 629
   Intended to be translated. It is displayed in a standard dialog with [Accept]
   [Reject] actions during the download/ installation process. Note, that click-through
   license must be specified for any feature that will be selected for installation
-  or update using the Eclipse update manager. When using nested features, only
+   or update using the Eclipse update manager. When using nested features,
- the nesting parent (ie. the feature selected for installation or update) must
+ only the nesting parent (ie. the feature selected for installation or update)
- have click-through license text defined. The license text is required even
+ must have click-through license text defined. The license text is required
- if the optional <i>url</i> attribute is specified.</li>
+ even if the optional <i>url</i> attribute is specified.</li>
    <ul>
     <li> url - optional URL for the full description as HTML. The URL can
-Line 650
+Line 656
      <li> label - displayable label (name) for the referenced site</li>
      </ul>
-     <li> &lt;discovery&gt; - URL to go to for new features. In general, a
+      <li> &lt;discovery&gt; - URL to go to for new features. In general,
- provider  can use this element to reference its own site(s), or site(s) of
+ a  provider  can use this element to reference its own site(s), or site(s)
- partners  that offer complementary features. Eclipse uses this element simply
+ of  partners  that offer complementary features. Eclipse uses this element
- as a way to distribute new site URLs to the clients</li>
+ simply  as a way to distribute new site URLs to the clients</li>
      <ul>
     <li> url - actual URL</li>
-Line 662
+Line 668
      </ul>
    </ul>
-     <li> &lt;includes&gt; - optional reference to a nested feature that is
+      <li> &lt;includes&gt; - optional reference to a nested feature that
-  considered to be part of this feature. Nested features must be located on
+ is  considered to be part of this feature. Nested features must be located
-  the same update site as this feature</li>
+ on  the same update site as this feature</li>
    <ul>
     <li> id - required nested feature identifier</li>
      <li> version - required nested feature version</li>
        <li> name- optional displayable label (name). Intended to be translated.</li>
-       <li>optional - optional specification indicating if this included feature
+        <li>optional - optional specification indicating if this included
-  can be optionally installed. Default is "false"<br>
+ feature  can be optionally installed. Default is "false"<br>
        </li>
        <li>match&nbsp; - optional rule that will be applied when resolving
  the feature reference. A <samp>perfect</samp> match (the default that matches
-Line 682
+Line 688
   consideration, while <samp>greaterOrEqual</samp> simply allows any version
   that is more recent or identical to the one specified).</li>
        <li>search_location&nbsp; - optional. Indicates whether the "New Updates"
-  action should search the update location determined by the nesting root
+  action should search the update location determined by the nesting root feature
- feature  (<tt>root</tt>, is the default), or the location defined by the
+  (<tt>root</tt>, is the default), or the location defined by the nested feature
- nested feature  (<tt>self</tt>), or search both (<tt>both</tt>) in that order
+  (<tt>self</tt>), or search both (<tt>both</tt>) in that order (root first,
- (root first,  self if nothing is found).</li>
+  self if nothing is found).</li>
    </ul>
-     <li> &lt;requires&gt; - optional feature dependency information. Is expressed
+      <li> &lt;requires&gt; - optional feature dependency information. Is
-  in terms of plug-in dependencies. If specified, is enforced by the installation
+ expressed  in terms of plug-in dependencies. If specified, is enforced by
-  and update support at the time of installation</li>
+ the installation   and update support at the time of installation</li>
    <ul>
-    <li> &lt;import&gt; - dependency entry. Specification and processing is
+     <li> &lt;import&gt; - dependency entry. Specification and processing
-  a subset of the &lt;import&gt; specification in plugin.xml</li>
+ is  a subset of the &lt;import&gt; specification in plugin.xml</li>
      <ul>
     <li> plugin - identifier of dependent plug-in.</li>
-Line 703
+Line 709
   be specified.</li>
      <li> version - optional plug-in/feature version specification</li>
          <li>patch - optional specification indicating if this feature is
- a  patch of the dependant feature. Default is "false". If patch is true,
+ a  patch of the dependant feature. Default is "false". If patch is true, version
- version  must be specified. If patch is true, only feature must be specified.
+  must be specified. If patch is true, only feature must be specified. If
- If patch  is true, and match is specified, it must be 'perfect'.<br>
+ patch  is true, and match is specified, it must be 'perfect'.<br>
          </li>
      <li> match - optional matching rule. Valid values and processing are
  as  follows:</li>
-Line 721
+Line 727
      <li> <b><i>perfect</i></b> - dependent plug-in version must match exactly
   the specified version.</li>
      <li> <b><i>equivalent</i></b> - dependent plug-in version must be at
- least  at the version specified, or at a higher service level (major and
+ least  at the version specified, or at a higher service level (major and minor
- minor version  levels must equal the specified version).</li>
+ version  levels must equal the specified version).</li>
      <li> <b><i>compatible</i></b> - dependent plug-in version must be at
  least  at the version specified, or at a higher service level or minor level
  (major  version level must equal the specified version).</li>
-Line 744
+Line 750
  plug-in  fragment. Default is "false"</li>
      <li> os - optional operating system specification. A comma-separated
  list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
-  . Indicates this entry should only be installed on one of the specified
+  . Indicates this entry should only be installed on one of the specified os
- os  systems. If this attribute is not specified, the entry can be installed
+  systems. If this attribute is not specified, the entry can be installed
- on all systems (portable implementation). This information is used as a hint
+  on all systems (portable implementation). This information is used as a
-  by the installation and update support (user can force installation of entry
+ hint  by the installation and update support (user can force installation
-  regardless of this setting).</li>
+ of entry  regardless of this setting).</li>
      <li> arch - optional machine architecture specification. A comma-separated
   list of architecture designators defined by Eclipse (see Javadoc for <tt>
   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
-Line 758
+Line 764
   can force installation of feature regardless of this setting).</li>
      <li> ws - optional windowing system specification. A comma-separated
  list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
-  . Indicates this entry should only be installed on one of the specified
+  . Indicates this entry should only be installed on one of the specified ws
- ws  systems. If this attribute is not specified, the entry can be installed
+  systems. If this attribute is not specified, the entry can be installed
- on all systems (portable implementation). This information is used as a hint
+  on all systems (portable implementation). This information is used as a
-  by the installation and update support (user can force installation of entry
+ hint  by the installation and update support (user can force installation
-  regardless of this setting).</li>
+ of entry  regardless of this setting).</li>
      <li> nl - optional locale specification. A comma-separated list of locale
   designators defined by Java. Indicates this entry should only be installed
   on a system running with a compatible locale (using Java locale-matching
-Line 774
+Line 780
  indicating  the download size in KBytes of the referenced plug-in archive.
  If not specified,  the download size is not known (<b>Implementation Note:</b>
  the implementation  needs to distinguish between "not known" and 0 size)</li>
-     <li> install-size - optional hint supplied by the feature packager, indicating
+      <li> install-size - optional hint supplied by the feature packager,
-  the install size in KBytes of the referenced plug-in archive. If not specified,
+ indicating   the install size in KBytes of the referenced plug-in archive.
-  the install size is not known (<b>Implementation Note:</b> the implementation
+ If not specified,   the install size is not known (<b>Implementation Note:</b>
-  needs to distinguish between "not known" and 0 size)</li>
+ the implementation   needs to distinguish between "not known" and 0 size)</li>
    </ul>
      <li> &lt;data&gt; - identifies non-plugin data that is part of the feature</li>
-Line 786
+Line 792
     <li> id - required data identifier in the form of a relative path.</li>
      <li> os - optional operating system specification. A comma-separated
  list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
-  . Indicates this entry should only be installed on one of the specified
+  . Indicates this entry should only be installed on one of the specified os
- os  systems. If this attribute is not specified, the entry can be installed
+  systems. If this attribute is not specified, the entry can be installed
- on all systems (portable implementation). This information is used as a hint
+  on all systems (portable implementation). This information is used as a
-  by the installation and update support (user can force installation of entry
+ hint  by the installation and update support (user can force installation
-  regardless of this setting).</li>
+ of entry  regardless of this setting).</li>
      <li> arch - optional machine architecture specification. A comma-separated
   list of architecture designators defined by Eclipse (see Javadoc for <tt>
   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
-Line 800
+Line 806
   can force installation of feature regardless of this setting).</li>
      <li> ws - optional windowing system specification. A comma-separated
  list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
-  . Indicates this entry should only be installed on one of the specified
+  . Indicates this entry should only be installed on one of the specified ws
- ws  systems. If this attribute is not specified, the entry can be installed
+  systems. If this attribute is not specified, the entry can be installed
- on all systems (portable implementation). This information is used as a hint
+  on all systems (portable implementation). This information is used as a
-  by the installation and update support (user can force installation of entry
+ hint  by the installation and update support (user can force installation
-  regardless of this setting).</li>
+ of entry  regardless of this setting).</li>
      <li> nl - optional locale specification. A comma-separated list of locale
   designators defined by Java. Indicates this entry should only be installed
   on a system running with a compatible locale (using Java locale-matching
-Line 816
+Line 822
  indicating  the download size in KBytes of the referenced data archive. If
  not specified,  the download size is not known (<b>Implementation Note:</b>
  the implementation  needs to distinguish between "not known" and 0 size)</li>
-     <li> install-size - optional hint supplied by the feature packager, indicating
+      <li> install-size - optional hint supplied by the feature packager,
-  the install size in KBytes of the referenced data archive. If not specified,
+ indicating   the install size in KBytes of the referenced data archive. If
-  the install size is not known (<b>Implementation Note:</b> the implementation
+ not specified,   the install size is not known (<b>Implementation Note:</b>
-  needs to distinguish between "not known" and 0 size)</li>
+ the implementation   needs to distinguish between "not known" and 0 size)</li>
    </ul>
-Line 849
+Line 855
   mechanism). </p>
  <h3> <a name="Plug-In_Archive"></a> Plug-In Archive</h3>
-    Plug-ins and plug-in fragments are individually packaged as separate Java
+     Plug-ins and plug-in fragments are individually packaged as separate
-  .jars. Standard Java jar facilities are used for constructing plug-in archives.
+ Java   .jars. Standard Java jar facilities are used for constructing plug-in
-  There is no distinction made between a plug-in archive containing a plug-in
+ archives.   There is no distinction made between a plug-in archive containing
-  and one containing a plug-in fragment.
+ a plug-in   and one containing a plug-in fragment.
  <p>The recommended convention for naming the plug-in archives is <br>
    <tt>&lt;id&gt;_&lt;version&gt;.jar</tt> </p>
-Line 866
+Line 872
    <tt>org.eclipse.ui.nl_2.0.jar</tt> <br>
    <tt>my_plugin.jar</tt> </p>
- <p>Internally, each plug-in archive packages all the relevant plug-in or fragment
+ <p>Internally, each plug-in archive packages all the relevant plug-in or
- files relative to its plug-in or fragment directory (but not including the
+ fragment files relative to its plug-in or fragment directory (but not including
- directory path element). The archive has the following structure </p>
+ the directory path element). The archive has the following structure </p>
  <p><tt>plugin.xml *OR* fragment.xml</tt> <br>
    <tt>other plug-in or feature files and subdirectories</tt> <br>
-Line 883
+Line 889
  <p>This mechanism cannot be used for translating the actual packaging information
   that is part of the installation xml files. Consequently the standard Java
-  translation conventions are used for the packaging information, and all necessary
+   translation conventions are used for the packaging information, and all
- translations must be available at the time the feature is packaged. </p>
+ necessary translations must be available at the time the feature is packaged.
+ </p>
  <h4> <a name="Translated_Feature_Information"></a> Translated Feature Information</h4>
     <b>Note:</b> This section describes the conventions used for translating
   the information contained within the feature manifest. It allows for the
- update client to select the correctly localized strings from the update server.
+  update client to select the correctly localized strings from the update
-  This section specifically does not describe localization of individual plug-ins.
+ server.  This section specifically does not describe localization of individual
+ plug-ins.
  <p>Several of the attributes within the feature manifest are strings intended
   for display through user interfaces. To facilitate translation, these attribute
   values use the convention defined for translatable attributes of plugin.xml.
-  Strings beginning with % up to the first space are treated as resource identifier
+   Strings beginning with % up to the first space are treated as resource
-  keys (without the %) and looked up in a properties file. For example </p>
+ identifier  keys (without the %) and looked up in a properties file. For
+ example </p>
  <p><tt>label="%cfg Tool Feature for Linux"</tt> </p>
  <p>results in a resource lookup in the correct property file with key "cfg".
-  If no property files are supplied, or the key is not found the default string
+   If no property files are supplied, or the key is not found the default
-  value (following the %key) is used. </p>
+ string  value (following the %key) is used. </p>
  <p>The property files are named as feature_&lt;locale&gt;.properties using
-  the Java resource bundle naming conventions. Within the feature archive .jar
+   the Java resource bundle naming conventions. Within the feature archive
- they are placed in the same directory as their corresponding feature.xml file.
+ .jar they are placed in the same directory as their corresponding feature.xml
-  </p>
+ file.  </p>
  <p><b>Implementation Note</b>: When accessing the resource bundles the Eclipse
-  installation and update code should create a class loader for accessing
+  installation and update code should create a class loader for accessing the
- the  translated string. This way, the standard locale lookup algorithm implemented
+  translated string. This way, the standard locale lookup algorithm implemented
   by Java is automatically used. </p>
  <p><tt>ResourceBundle b;</tt> <br>
-Line 945
+Line 953
  <p>Eclipse does not specify the format of the non-plug-in files. </p>
  <h3> <a name="Custom_Install_Handling"></a> Custom Install Handling</h3>
-    Custom install handlers are written as a Java class and are packaged as
+     Custom install handlers are written as a Java class and are packaged
- part of the <a href="#Feature_Archive">feature archive</a> . The installer
+ as  part of the <a href="#Feature_Archive">feature archive</a> . The installer
  must implement the <tt>IInstallHandler</tt> interface (in most cases will
  extend the <tt>BaseInstallHandler</tt> abstract helper class which implements
  <tt>IInstallHandler</tt>). When required, the install handler is dynamically
-Line 954
+Line 962
  during its processing. The install handler code has visibility to classes
  from the installation and update support plug-in, and its prerequisite plug-ins.
- <p><b>Implementation Note:</b> the detailed list of visible prerequisite plug-ins
+ <p><b>Implementation Note:</b> the detailed list of visible prerequisite
- is still evolving. It is expected to include <tt>org.eclipse.core.boot </tt>
+ plug-ins is still evolving. It is expected to include <tt>org.eclipse.core.boot
- and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt>
+ </tt> and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt>
-   and <tt>org.eclipse.swt</tt> when running with full workbench (ie. not
+   and <tt>org.eclipse.swt</tt> when running with full workbench (ie. not "headless
- "headless  mode"). Also, it would be useful to always expose <tt>org.eclipse.core.ant</tt>
+  mode"). Also, it would be useful to always expose <tt>org.eclipse.core.ant</tt>
    so that build scripts can be used as part of the install handler implementation.
   </p>
-Line 969
+Line 977
  <ul>
     <li> install-initiated - the install handler is called after a feature
- was selected for installation, but before any files were downloaded. It is
+  was selected for installation, but before any files were downloaded. It
- intended  to implement any custom click-through or user registration dialogs.
+ is  intended  to implement any custom click-through or user registration
- The base implementation of this method supplied with the abstract class <tt>BaseInstallHandler
+ dialogs.  The base implementation of this method supplied with the abstract
-      </tt>performs the default click-through processing using the license
+ class <tt>BaseInstallHandler       </tt>performs the default click-through
-  text supplied as part of the feature manifest. On return this method indicates
+ processing using the license  text supplied as part of the feature manifest.
-  success (installation continues) of failure (installation is aborted).</li>
+ On return this method indicates  success (installation continues) of failure
+ (installation is aborted).</li>
      <li> install-downloaded - the install handler is called after all the
  required  feature files were downloaded (feature, plugins, data) but before
  the actual  installation is performed. The install handler is expected to
-Line 982
+Line 991
  other pre-install processing.&nbsp; On return this method indicates success
  (installation continues) or failure (installation is aborted).</li>
      <li> install-completion - the install handler is called after the feature
-  information and the plug-ins were installed. It is expected to complete
+  information and the plug-ins were installed. It is expected to complete the
- the  installation of any non-plug-in data that was part of the feature. On
+  installation of any non-plug-in data that was part of the feature. On return
- return  this method indicates success (returns custom install log) or failure
+  this method indicates success (returns custom install log) or failure (installation
- (installation  is aborted). On failure, the install handler is expected to
+  is aborted). On failure, the install handler is expected to perform any
- perform any required cleanup.</li>
+ required cleanup.</li>
      <li> uninstall-initiated - the install handler is called when a feature
   is selected for removal, but before any of the standard uninstall processing
   has taken place. It is passed the custom install log created by the install
-Line 1000
+Line 1009
  in  their own jars (even though they could be just exposed in the feature
  archive  jar). The jar should be signed, and sealed.
  <h3> <a name="Security_Considerations"></a> Security Considerations</h3>
-    The general approach is to use base Java jar signing for the feature and
+     The general approach is to use base Java jar signing for the feature
-  plug-in archive .jars.
+ and   plug-in archive .jars.
  <p>Features are verified as follows: </p>
  <ul>
-Line 1028
+Line 1037
  (originator is trusted for this installation).
  <h2> <a name="Update_Server"></a> Update Server</h2>
     The default Eclipse update server is any URL-accessible server. The default
-  implementation assumes a fixed-layout server. The content of the server (in
+   implementation assumes a fixed-layout server. The content of the server
- terms of available features and plug-ins) is described in a site map file,
+ (in terms of available features and plug-ins) is described in a site map
- <i>site.xml</i>. This file can be manually maintained, or can be dynamically
+ file, <i>site.xml</i>. This file can be manually maintained, or can be dynamically
   computed by the server.
  <h3> <a name="Site_Map"></a> Site Map</h3>
-    The update server URL can be specified as a full URL to the site map file,
+     The update server URL can be specified as a full URL to the site map
-  or a URL of a directory path containing the site map file (similar to index.html
+ file,   or a URL of a directory path containing the site map file (similar
-  processing). The site map site.xml format is defined by the following dtd:
+ to index.html   processing). The site map site.xml format is defined by the
+ following dtd:
  <p><tt>&lt;?xml encoding="ISO-8859-1"?&gt;</tt> </p>
  <p><tt>&lt;!ELEMENT site (description?, feature*, archive*, category-def*)&gt;</tt>
-Line 1109
+Line 1118
   string registered via the <a href="#Framework">install framework</a>  extension
  point. If not specified, the type is assumed to be the default Eclipse site
  type (as specified in this document).</li>
-     <li> url - optional URL defining the update site baseline URL (used to
+      <li> url - optional URL defining the update site baseline URL (used
-  determine individual &lt;feature&gt; and &lt;archive&gt; location).&nbsp;
+ to  determine individual &lt;feature&gt; and &lt;archive&gt; location).&nbsp;
   Can be relative or absolute. If relative, is relative to site.xml. If not
   specified, the default is the URL location of the site.xml file.</li>
-Line 1123
+Line 1132
  be  specified as absolute of relative. If relative, If relative, is relative
  to site.xml.</li>
      <br>
-   Note, that for NL handling the URL value should be separated to allow alternate
+    Note, that for NL handling the URL value should be separated to allow
-  URLs to be specified for each national language.
+ alternate  URLs to be specified for each national language.
    </ul>
      <li> &lt;feature&gt; - identifies referenced feature archive</li>
    <ul>
-    <li> type - optional feature type specification. The value refers to a
+     <li> type - optional feature type specification. The value refers to
- type  string registered via the <a href="#Framework">install framework</a>
+ a  type  string registered via the <a href="#Framework">install framework</a>
    extension point. If not specified, the type is assumed to be the default
-  feature type for the site. If the site type is the default Eclipse site
+  feature type for the site. If the site type is the default Eclipse site type,
- type,  the default feature type is the packaged feature type (as specified
+  the default feature type is the packaged feature type (as specified in this
- in this  document).</li>
+  document).</li>
-     <li> id - optional feature identifier. The information is used as a performance
+      <li> id - optional feature identifier. The information is used as a
-  optimization to speed up searches for features. Must match the identifier
+ performance   optimization to speed up searches for features. Must match
-  specified in the feature.xml of the referenced archive (the url attribute).
+ the identifier   specified in the feature.xml of the referenced archive (the
-  If specified, the version attribute must also be specified.</li>
+ url attribute).   If specified, the version attribute must also be specified.</li>
-     <li> version - optional feature version. The information is used as a
+      <li> version - optional feature version. The information is used as
- performance  optimization to speed up searches for features. Must match the
+ a  performance  optimization to speed up searches for features. Must match
- version specified in the feature.xml of the referenced archive (the url attribute).
+ the  version specified in the feature.xml of the referenced archive (the
- If specified, the id attribute must also be specified.</li>
+ url attribute).  If specified, the id attribute must also be specified.</li>
      <li> url - required URL reference to the feature archive. Can be relative
   or absolute. If relative, it is relative to the location of the site.xml
- file.       <b>Note</b>: the default site implementation allows features
+ file.       <b>Note</b>: the default site implementation allows features to
- to be accessed without being explicitly declared using a &lt;feature&gt;
+ be accessed without being explicitly declared using a &lt;feature&gt; entry.
- entry. By default, an undeclared features reference is interpreted as "features/&lt;id&gt;_&lt;version&gt;.jar"</li>
+ By default, an undeclared features reference is interpreted as "features/&lt;id&gt;_&lt;version&gt;.jar"</li>
       <li>label - optional feature label. The value is used for optimization
  when browsing the site from the update manager. Intended to be translated.<br>
      </li>
      <li> os - optional operating system specification. A comma-separated
  list  of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
   . Indicates this feature should only be installed on one of the specified
-  os systems. If this attribute is not specified, the feature can be installed
+   os systems. If this attribute is "*", the feature can be installed   on
-  on all systems (portable implementation). This information is used as a hint
+ all systems (portable implementation). This information is used as a hint
  by the installation and update support (user can force installation of feature
  regardless of this setting).</li>
      <li> arch - optional machine architecture specification. A comma-separated
   list of architecture designators defined by Eclipse (see Javadoc for <tt>
   org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only
-  be installed on one of the specified systems. If this attribute is not specified,
+  be installed on one of the specified systems. If this attribute&nbsp;is
-  the feature can be installed on all systems (portable implementation). This
+ "*",  the feature can be installed on all systems (portable implementation).
-  information is used as a hint by the installation and update support (user
+ This  information is used as a hint by the installation and update support
-  can force installation of feature regardless of this setting).</li>
+ (user  can force installation of feature regardless of this setting).</li>
      <li> ws - optional windowing system specification. A comma-separated
  list  of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt>
   . Indicates this feature should only be installed on one of the specified
-  ws systems. If this attribute is not specified, the feature can be installed
+   ws systems. If this attribute&nbsp;is "*", the feature can be installed
-  on all systems (portable implementation). This information is used as a hint
+   on all systems (portable implementation). This information is used as a
- by the installation and update support (user can force installation of feature
+ hint by the installation and update support (user can force installation
- regardless of this setting).</li>
+ of feature regardless of this setting).</li>
      <li> nl - optional locale specification. A comma-separated list of locale
   designators defined by Java. Indicates this feature should only be installed
   on a system running with a compatible locale (using Java locale-matching
- rules). If this attribute is not specified, the feature can be installed
+ rules). If this attribute&nbsp;is "*", the feature can be installed on all
- on all systems (language-neutral implementation). This information is used
+ systems (language-neutral implementation). This information is used as a
- as a hint by the installation and update support (user can force installation
+ hint by the installation and update support (user can force installation of
- of feature regardless of this setting).</li>
+ feature regardless of this setting).</li>
-     <li>patch - optional specification indicating if this feature is a  patch.
+      <li>patch - optional specification indicating if this feature is a
- Default is "false".&nbsp;</li>
+ patch. Default is "false".&nbsp;</li>
    </ul>
-     <li> &lt;archive&gt; - identifies referenced "storage" archive (the actual
+      <li> &lt;archive&gt; - identifies referenced "storage" archive (the
-  files referenced via the <tt>&lt;plugin&gt;</tt> or <tt>&lt;data&gt;</tt>
+ actual  files referenced via the <tt>&lt;plugin&gt;</tt> or <tt>&lt;data&gt;</tt>
-   elements in the feature manifest). The site simply manages archives as
+   elements in the feature manifest). The site simply manages archives as a
- a  path-to-URL map. The default Eclipse site implementation does not require
+  path-to-URL map. The default Eclipse site implementation does not require
   the &lt;archive&gt; section to be included in the site map (site.xml). Any
   archive reference not explicitly defined as part of an &lt;archive&gt; section
   is assumed to be mapped to a url in the form "&lt;archivePath&gt;" relative
-Line 1202
+Line 1211
    </ul>
      <li> &lt;category-def&gt; - an optional definition of a category that
- can be used by installation and update support to hierarchicaly organize features</li>
+  can be used by installation and update support to hierarchicaly organize
+ features</li>
    <ul>
     <li> name - category name. Is specified as a path of name tokens separated
-Line 1210
+Line 1220
      <li> label - displayable label. Intended to be translated.</li>
    </ul>
-     <li> &lt;category&gt; - actual category specification for a feature entry</li>
+      <li> &lt;category&gt; - actual category specification for a feature
+ entry</li>
    <ul>
    name - category name
-Line 1222
+Line 1233
  <p><tt>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</tt> </p>
  <p>Translatable text contained in the site.xml can be separated into site&lt;_locale&gt;.properties
-  files using Java property bundle conventions. Note that the translated strings
+   files using Java property bundle conventions. Note that the translated
-  are used at installation time (ie. do not employ the plug-in fragment runtime
+ strings  are used at installation time (ie. do not employ the plug-in fragment
-  mechanism). The property bundles are located relative to the site.xml location.
+ runtime  mechanism). The property bundles are located relative to the site.xml
-  </p>
+ location.   </p>
  <h3> <a name="Default_Site_Layout"></a> Default Site Layout</h3>
     <tt>&lt;site root&gt;/</tt> <br>
-Line 1251
+Line 1262
   servlets that compute the site.xml map, and control access to individual
  archives based on some user criteria)</li>
      <li> by supplying a custom concrete implementation of the site object
- (installed  on the client machine, update server specified <tt>&lt;site type=""&gt;</tt>
+  (installed  on the client machine, update server specified <tt>&lt;site
-  ). The custom concrete site implementation, together with any server-side
+ type=""&gt;</tt>  ). The custom concrete site implementation, together with
-  logic support the required control mechanisms.</li>
+ any server-side   logic support the required control mechanisms.</li>
  </ul>
     Eclipse provides an example demonstrating an implementation of an access
-Line 1284
+Line 1295
    <tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  META_INF/</tt>   </p>
- <p><b>Implementation Note:</b> we will go back to the original design of not
+ <p><b>Implementation Note:</b> we will go back to the original design of
- splitting out fragments (ie. plugin and fragments go into the same install
+ not splitting out fragments (ie. plugin and fragments go into the same install
   location) </p>
  <h3> <a name="Unmanaged_Plugins"></a> "Unmanaged" Plug-Ins</h3>
     Eclipse supports a concept of "unmanaged" plug-ins. These are plug-ins
  that were directly installed into the Eclipse file tree without being part
- of a feature (eg. developer unzipping plug-in archive directly into the Eclipse
+  of a feature (eg. developer unzipping plug-in archive directly into the
-  file tree).
+ Eclipse  file tree).
- <p>Eclipse runtime recognizes these plugins during startup and loads the plug-in
+ <p>Eclipse runtime recognizes these plugins during startup and loads the
- information into the runtime registry following the standard plug-in binding
+ plug-in information into the runtime registry following the standard plug-in
- rules. The update support also recognizes the presence of this new plug-in,
+ binding rules. The update support also recognizes the presence of this new
- but since this plug-in is not part of any feature it cannot be updated using
+ plug-in, but since this plug-in is not part of any feature it cannot be updated
- the update support (hence "unmanaged"). Unmanaged plug-in that become referenced
+ using the update support (hence "unmanaged"). Unmanaged plug-in that become
- by a feature as a result of some future installation or update action become
+ referenced by a feature as a result of some future installation or update
- "managed" (can be updated as part of the feature). </p>
+ action become "managed" (can be updated as part of the feature). </p>
  <p>Unmanaged plug-ins are not displayed as part of the installation and update
   UI. </p>
-Line 1315
+Line 1326
  sharing relationships. As a result, Eclipse <b>does not allow</b> plug-ins
  to be installed using native installers into the shared installation tree.
  Instead, native installers must establish their own installation root directory.
- The subdirectory structure is the same as defined for base Eclipse. The private
+  The subdirectory structure is the same as defined for base Eclipse. The
-  root directory is logically linked into the shared Eclipse installation
+ private  root directory is logically linked into the shared Eclipse installation
  via  a link file installed by the native installer. The file path for the
  link  file is <tt>&lt;configRoot&gt;/links/</tt>. The <tt>&lt;configRoot&gt;
  </tt>  location is computed by Eclipse relative to the launch <a
-Line 1326
+Line 1337
  <p>The name of the link file is not specified by Eclipse. The name is determined
   by the native installer. To minimize the potential for naming collisions,
-  it is recommended that the file name contain the identifier and version of
+   it is recommended that the file name contain the identifier and version
- the feature being installed by the native installer. For example, <tt>&lt;featureId&gt;_&lt;featureVersion&gt;.properties</tt>
+ of the feature being installed by the native installer. For example, <tt>&lt;featureId&gt;_&lt;featureVersion&gt;.properties</tt>
   . The file content is in the form of a Java properties file, with the following
   properties defined: </p>
  <p><tt>path=[r|rw] install-path[,[r|rw] install-path]*</tt> </p>
  <p>The property <tt>path</tt> is a comma-separated list of optionally annotated
-  install paths. The property value <tt>install-path</tt> is a full file path
+   install paths. The property value <tt>install-path</tt> is a full file
-  to the installation directory root, specified in local OS format. The optional
+ path  to the installation directory root, specified in local OS format. The
-  annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse update support
+ optional  annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse
-  should allow the specified location to be used for updates. Default is to
+ update support  should allow the specified location to be used for updates.
-  allow updates&nbsp; (w). </p>
+ Default is to  allow updates&nbsp; (w). </p>
  <p>Eclipse does not manage the linked directories in any way. It simply detects
   their existence by the presence of the link files, and includes the linked
-Line 1348
+Line 1359
    &nbsp; </p>
    <br>
   <br>
+  <br>
  </body>
  </html>

 Legend:



Removed from v.1.10
 


changed lines


 
Added in v.1.11
 Legend:



Removed from v.1.10
 


changed lines


 
Added in v.1.11
-Removed from v.1.10
+Added in v.1.11

help@eclipse.org	ViewVC Help
Powered by ViewVC 1.0.3