platform-update-home/doc/eclipse_update_packaging.html
Parent Directory
| 
Revision Log
Revision 1.9 - (view) (download) (as text)
| 1 : | droberts | 1.6 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
| 2 : | vlad | 1.1 | <html> |
| 3 : | <head> | ||
| 4 : | celek | 1.9 | |
| 5 : | <meta http-equiv="Content-Type" | ||
| 6 : | content="text/html; charset=iso-8859-1"> | ||
| 7 : | |||
| 8 : | celek | 1.7 | <meta name="Author" content="Lab User"> |
| 9 : | celek | 1.9 | |
| 10 : | celek | 1.7 | <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> |
| 11 : | <title>Eclipse Platform: Installation and Update</title> | ||
| 12 : | vlad | 1.1 | </head> |
| 13 : | celek | 1.7 | <body> |
| 14 : | celek | 1.9 | |
| 15 : | celek | 1.7 | <h1> Eclipse Platform<br> |
| 16 : | celek | 1.9 | Update Packaging Conventions</h1> |
| 17 : | <font size="-1">Revision Date: 12/05/2002 3:30PM - Version: 2.0.14</font><br> | ||
| 18 : | <a href="../../../../../hglegal.htm"><img src="ngibmcpy.gif" border="0" | ||
| 19 : | height="12" width="195"> | ||
| 20 : | </a> | ||
| 21 : | <p><b>Change History:</b> </p> | ||
| 22 : | celek | 1.7 | |
| 23 : | <ul> | ||
| 24 : | celek | 1.9 | <li><small>2.0.14<br> |
| 25 : | </small> | ||
| 26 : | <ul> | ||
| 27 : | <li><small>added <site><feature> label tag</small><br> | ||
| 28 : | </li> | ||
| 29 : | </ul> | ||
| 30 : | </li> | ||
| 31 : | celek | 1.7 | <li><font size="-1">2.0.13</font></li> |
| 32 : | celek | 1.9 | </ul> |
| 33 : | <ul> | ||
| 34 : | |||
| 35 : | celek | 1.7 | <ul> |
| 36 : | celek | 1.9 | <li><small>added <includes name,optional,match,search_location</small> |
| 37 : | celek | 1.7 | ></li> |
| 38 : | celek | 1.9 | <li><small>added <import feature,patch></small></li> |
| 39 : | |||
| 40 : | celek | 1.7 | </ul> |
| 41 : | celek | 1.9 | <li><font size="-1">2.0.12</font></li> |
| 42 : | |||
| 43 : | celek | 1.7 | <ul> |
| 44 : | celek | 1.9 | <li> <font size="-1">added reference to the <a |
| 45 : | href="http://www.eclipse.org/legal/updatemanager.html"> Eclipse.org Update | ||
| 46 : | Manager Agreement</a> </font></li> | ||
| 47 : | |||
| 48 : | </ul> | ||
| 49 : | <li> <font size="-1">2.0.11</font></li> | ||
| 50 : | |||
| 51 : | <ul> | ||
| 52 : | <li> <font size="-1"><feature> <license> is required</font></li> | ||
| 53 : | |||
| 54 : | </ul> | ||
| 55 : | <li> <font size="-1">2.0.10</font></li> | ||
| 56 : | |||
| 57 : | <ul> | ||
| 58 : | <li> <font size="-1"><feature colocation-affinity=""></font></li> | ||
| 59 : | |||
| 60 : | </ul> | ||
| 61 : | <li> <font size="-1">2.0.9</font></li> | ||
| 62 : | |||
| 63 : | <ul> | ||
| 64 : | <li> <font size="-1"><site> <feature> changes - additional | ||
| 65 : | markup to optionally expose feature identification information to speed up | ||
| 66 : | searches</font></li> | ||
| 67 : | <li> <font size="-1">removed obsolete text</font></li> | ||
| 68 : | <li> <font size="-1">web-triggered update not in 2.0</font></li> | ||
| 69 : | <li> <font size="-1">no assist in 2.0 for license/ "key file" handling | ||
| 70 : | celek | 1.7 | (individual application/ plugin responsibility)</font></li> |
| 71 : | celek | 1.9 | |
| 72 : | celek | 1.7 | </ul> |
| 73 : | celek | 1.9 | <li> <font size="-1">2.0.8</font></li> |
| 74 : | |||
| 75 : | celek | 1.7 | <ul> |
| 76 : | celek | 1.9 | <li> <font size="-1"><feature> <includes></font></li> |
| 77 : | |||
| 78 : | celek | 1.7 | </ul> |
| 79 : | celek | 1.9 | <li> <font size="-1">2.0.7</font></li> |
| 80 : | |||
| 81 : | celek | 1.7 | <ul> |
| 82 : | celek | 1.9 | <li> <font size="-1">support explicit xml markup for primary features</font></li> |
| 83 : | |||
| 84 : | celek | 1.7 | </ul> |
| 85 : | celek | 1.9 | <li> <font size="-1">2.0.6</font></li> |
| 86 : | |||
| 87 : | celek | 1.7 | <ul> |
| 88 : | celek | 1.9 | <li> <font size="-1">install handler markup changes</font></li> |
| 89 : | |||
| 90 : | celek | 1.7 | </ul> |
| 91 : | celek | 1.9 | <li> <font size="-1">2.0.5</font></li> |
| 92 : | |||
| 93 : | celek | 1.7 | <ul> |
| 94 : | celek | 1.9 | <li> <font size="-1">updates to security section</font></li> |
| 95 : | |||
| 96 : | celek | 1.7 | </ul> |
| 97 : | celek | 1.9 | <li> <font size="-1">2.0.4</font></li> |
| 98 : | |||
| 99 : | celek | 1.7 | <ul> |
| 100 : | celek | 1.9 | <li> <font size="-1">general text cleanup</font></li> |
| 101 : | <li> <font size="-1"><feature><group> support removed (will | ||
| 102 : | celek | 1.7 | not be in Eclipse 2.0)</font></li> |
| 103 : | celek | 1.9 | <li> <font size="-1">arch= support added to <feature> and <feature><plugin></font></li> |
| 104 : | <li> <font size="-1">os=/ arch=/ ws=/ nl= added to <fetaure><data></font></li> | ||
| 105 : | <li> <font size="-1"><site url=""> new semantics</font></li> | ||
| 106 : | <li> <font size="-1">corrected errors in native installer link support</font></li> | ||
| 107 : | <li> <font size="-1">defined callback query strings for browser-triggered | ||
| 108 : | celek | 1.7 | processing</font></li> |
| 109 : | celek | 1.9 | |
| 110 : | celek | 1.7 | </ul> |
| 111 : | celek | 1.9 | |
| 112 : | celek | 1.7 | </ul> |
| 113 : | celek | 1.9 | |
| 114 : | celek | 1.7 | <h3> <font size="+2">Table of Contents</font></h3> |
| 115 : | celek | 1.9 | <a href="#Introduction">Introduction</a> <br> |
| 116 : | <a href="#Changes_from_R1.0">Changes | ||
| 117 : | from 1.0</a> <br> | ||
| 118 : | <a href="#Concepts">Concepts</a> <br> | ||
| 119 : | <a href="#Framework">Framework</a> | ||
| 120 : | <br> | ||
| 121 : | <a href="#Packaging_Conventions">Packaging Conventions</a> <br> | ||
| 122 : | <a href="#Feature_Archive">Feature | ||
| 123 : | Archive</a> <br> | ||
| 124 : | <a href="#Plug-In_Archive">Plug-In | ||
| 125 : | Archive</a> <br> | ||
| 126 : | <a href="#Packaging_NL">Packaging NL</a> | ||
| 127 : | <br> | ||
| 128 : | <a | ||
| 129 : | href="#Translated_Feature_Information"> Translated Feature Information</a> | ||
| 130 : | <br> | ||
| 131 : | <a | ||
| 132 : | href="#Translated_Plug-In_Information"> Translated Plug-In Information</a> | ||
| 133 : | <br> | ||
| 134 : | <a | ||
| 135 : | href="#Packaging_Target-Specific_Support"> Packaging Target-Specific Support</a> | ||
| 136 : | <br> | ||
| 137 : | <a | ||
| 138 : | href="#Packaging_Attribution_Information"> Packaging Attribution Information</a> | ||
| 139 : | <br> | ||
| 140 : | <a | ||
| 141 : | href="#Packaging_Attribution_Information"> Packaging Non-Plug-In Files</a> | ||
| 142 : | <br> | ||
| 143 : | <a | ||
| 144 : | href="#Packaging_Attribution_Information"> Custom Install Handling</a> | ||
| 145 : | <br> | ||
| 146 : | <a href="#Security_Considerations">Security | ||
| 147 : | Considerations</a> <br> | ||
| 148 : | <a href="#Update_Server">Update Server</a> <br> | ||
| 149 : | <a href="#Site_Map">Site Map</a> <br> | ||
| 150 : | <a href="#Default_Site_Layout">Default | ||
| 151 : | Site Layout</a> <br> | ||
| 152 : | <a href="#Controlling_Access">Controlling | ||
| 153 : | Access</a> <br> | ||
| 154 : | <a href="#Eclipse_Install">Eclipse Install</a> <br> | ||
| 155 : | <a href="#Default_Install_Layout">Default | ||
| 156 : | Install Layout</a> <br> | ||
| 157 : | <a href="#Unmanaged_Plugins">"Unmanaged" | ||
| 158 : | Plug-Ins</a> <br> | ||
| 159 : | <a | ||
| 160 : | href="#Using_Native_Platform_Installers"> Using Native Platform Installers</a> | ||
| 161 : | |||
| 162 : | <h2> <a name="Introduction"></a> Introduction</h2> | ||
| 163 : | This document outlines the support for managing the delivery of function | ||
| 164 : | within the Eclipse platform. Also refer to the "<a | ||
| 165 : | href="http://www.eclipse.org/legal/updatemanager.html"> Eclipse.org Update | ||
| 166 : | Manager Agreement</a> " for additional legal information governing the use | ||
| 167 : | of the Eclipse update manager function. | ||
| 168 : | <h3> <a name="Changes_from_R1.0"></a> Changes from R1.0</h3> | ||
| 169 : | This section describes the major design changes from the R1.0 Installation | ||
| 170 : | and Update support and supplies rationale for each design change. | ||
| 171 : | celek | 1.7 | <ul> |
| 172 : | celek | 1.9 | <li> <b>extendable framework</b></li> |
| 173 : | <br> | ||
| 174 : | In R2.0 Eclipse defines an extendable framework for installation and update, | ||
| 175 : | allowing the support for alternate packaging and site management schemes. | ||
| 176 : | R2.0 supplies a default concrete implementation of this framework. <li> <b> | ||
| 177 : | celek | 1.7 | feature support</b></li> |
| 178 : | celek | 1.9 | <br> |
| 179 : | In R2.0 the concept of a <i>component</i> and <i>configuration</i> is merged | ||
| 180 : | into <i>feature</i>. Features define the packaging structure for a group of | ||
| 181 : | related plug-ins, plug-in fragments, and optionally non-plug-in files. Features | ||
| 182 : | are treated purely as an installation and packaging construct. They do not | ||
| 183 : | play a role during Eclipse plug-in execution. Features do not nest. They | ||
| 184 : | are simply an inclusive "manifest" of the plug-ins, fragments and other files | ||
| 185 : | that make up that feature. If features are logically made up of plug-ins from | ||
| 186 : | "sub-features", the top-level feature "manifest" must be fully resolved at | ||
| 187 : | packaging time. <li> <b>default feature archive format</b></li> | ||
| 188 : | <br> | ||
| 189 : | R1.0 components were packaged as a single Java .jar containing the component | ||
| 190 : | manifest as well as the actual plug-in files. The problem with this approach | ||
| 191 : | is lack of granularity at download time. In R2.0, the feature archive consists | ||
| 192 : | of multiple separate .jars - one .jar per plug-in and fragment, plus one .jar | ||
| 193 : | for the actual feature information. The Installation and Update support selectively | ||
| 194 : | downloads only those jars required for the installation. <li> <b>site map</b></li> | ||
| 195 : | <br> | ||
| 196 : | Default Eclipse update server must contain a <i>site map</i> file (site.xml). | ||
| 197 : | This is an evolution of the R1.0 install.index support. The rationale for | ||
| 198 : | using a structured site defined by the map rather than a "free form" web | ||
| 199 : | site, is the ability to present a consistent installation experience for | ||
| 200 : | the user. Also, this provides the necessary structure for discovery of available | ||
| 201 : | updates. Additional support for "free form" browsing may be considered in | ||
| 202 : | future work. <li> <b>using native install/ uninstall</b></li> | ||
| 203 : | <br> | ||
| 204 : | The primary mechanism for installing and updating Eclipse features is the | ||
| 205 : | built-in installation and update support. Some products may instead choose | ||
| 206 : | to use native installer technology (eg. MSI, RPM, etc) to deliver Eclipse | ||
| 207 : | features. However, native installers do not implement the required support | ||
| 208 : | for understanding the Eclipse installation structure. In particular, the native | ||
| 209 : | uninstallers will, by default, remove plug-in files that were installed using | ||
| 210 : | the native installer without regard to these plug-ins being needed by other | ||
| 211 : | features. As a result, features installed using native installers must be | ||
| 212 : | written into private product-specific installation location and not the shared | ||
| 213 : | Eclipse installation location. The shared Eclipse is made aware of the produce-specific | ||
| 214 : | location via an installed "link file". <li> <b>custom install handling</b></li> | ||
| 215 : | <br> | ||
| 216 : | In many cases the standard installation handling supplied by Eclipse is | ||
| 217 : | not be sufficient to handle various custom requirements. To accommodate this, | ||
| 218 : | R2.0 Eclipse supports custom install handlers packaged as part of the feature | ||
| 219 : | celek | 1.7 | and executed during the feature installation. <li> <b>path naming conventions</b></li> |
| 220 : | celek | 1.9 | <br> |
| 221 : | R1.0 mandated the use of the various identifiers and versions inside the | ||
| 222 : | packaged archives (eg. directory path names for plug-ins). This approach | ||
| 223 : | has proven to be ackward and error prone. In 2.0, the packaging requirements | ||
| 224 : | no longer mandate that path names of packaged files precisely reflect the | ||
| 225 : | contained identifiers and versions. The properly identified install subdirectories | ||
| 226 : | are created by the Eclipse support during the installation and update process | ||
| 227 : | based on the archive content (rather than explicit jar path structure set | ||
| 228 : | up at packaging time) | ||
| 229 : | celek | 1.7 | </ul> |
| 230 : | celek | 1.9 | |
| 231 : | <h3> <a name="Concepts"></a> Concepts</h3> | ||
| 232 : | <b>Plug-in</b> <br> | ||
| 233 : | Eclipse developers build plug-ins. Plug-ins are the base units of execution | ||
| 234 : | recognized by the Eclipse runtime environment. In general, plug-ins are | ||
| 235 : | not exposed to users that select function during installation or update. | ||
| 236 : | The reason is that plug-in boundaries are established by developers for development | ||
| 237 : | reasons (like function reuse) and present the wrong level of granularity in | ||
| 238 : | terms of what the user sees as the unit of function. | ||
| 239 : | <p>While plug-ins are being developed (ie. are frequently being changed), | ||
| 240 : | their internal file structure will reflect what is convenient to the developer. | ||
| 241 : | This will generally depend on the particular development tool being used. | ||
| 242 : | Typically, however, the developer will likely setup the plug-in to execute | ||
| 243 : | from a directory tree containing exposed .class files, rather than executing | ||
| 244 : | from a .jar (requires an extra step to create the .jar and we all know developers | ||
| 245 : | hate extra steps). Also, at this stage the developer does not pay particular | ||
| 246 : | attention to plug-in versioning information, because the plug-in is continually | ||
| 247 : | celek | 1.7 | changing. </p> |
| 248 : | celek | 1.9 | |
| 249 : | <p>However, when the plug-in is ready to be packaged, it needs to be converted | ||
| 250 : | to a form suitable for packaging and installation. Typically it means creation | ||
| 251 : | of the runtime .jar(s) and removing any development-time files (source, | ||
| 252 : | exposed .class files, etc). It also means updating the plugin.xml manifest | ||
| 253 : | with the formal plug-in version and reflecting the version in the plug-in | ||
| 254 : | directory name (see "Concurrent Plug-In Version Support" for details). </p> | ||
| 255 : | |||
| 256 : | celek | 1.7 | <p><b>Plug-in Fragment</b> <br> |
| 257 : | celek | 1.9 | Plug-in Fragments (or simply Fragments) allow independent packaging of certain |
| 258 : | aspects of the base plug-in. This includes (but may not be limited to) translated | ||
| 259 : | resources for the plug-in, OS-specific or windowing-system-specific code. | ||
| 260 : | At runtime, fragments are logically merged into the base plug-in. From a packaging | ||
| 261 : | point of view, the install and update support does not really differentiate | ||
| 262 : | celek | 1.7 | between plug-ins and their related fragments. </p> |
| 263 : | celek | 1.9 | |
| 264 : | celek | 1.7 | <p><b>Feature</b> <br> |
| 265 : | celek | 1.9 | A feature is an installation packaging mechanism used to define a group |
| 266 : | of versioned plug-ins and/or plug-in fragments plus non-plug-in files that | ||
| 267 : | is used to deliver some user function. A feature can also include other features. | ||
| 268 : | Features are exposed to users as part of the packaging and installation process, | ||
| 269 : | because they represent a unit of function selection. Features also represent | ||
| 270 : | celek | 1.7 | a unit of installation. Features carry a version identifier.</p> |
| 271 : | celek | 1.9 | |
| 272 : | <p>Features are packaged as a feature archive, referencing the required plug-ins, | ||
| 273 : | plug-in fragments and optional non-plug-in files. The feature archives are | ||
| 274 : | placed on an update server for download and installation by the Eclipse update | ||
| 275 : | manager, or they can be used as the input into a formal packaging process | ||
| 276 : | using one of the "traditional" installer technologies. The format of the feature | ||
| 277 : | archive is described later. </p> | ||
| 278 : | |||
| 279 : | <h3> <a name="Framework"></a> Framework</h3> | ||
| 280 : | The 2.0 installation and update support is provided as a framework that | ||
| 281 : | allows custom implementations to be supplied for its key elements. In particular, | ||
| 282 : | the following can be supplied: | ||
| 283 : | vlad | 1.1 | <ul> |
| 284 : | celek | 1.9 | <li> concrete implementations of feature (IFeature interface) that can |
| 285 : | be used to support alternate packaging schemes. New concrete feature types | ||
| 286 : | are registere via the "org.eclipse.update.featureTypes" extension point.</li> | ||
| 287 : | <li> concrete implementations of site (ISite interface) that can be used | ||
| 288 : | to support alternate site layout, or site behavior. New concrete site types | ||
| 289 : | are registered via the "org.eclipse.update.siteTypes" extension point.</li> | ||
| 290 : | <li> each feature can specify a custom install handler as part of its | ||
| 291 : | feature manifest. Install handlers (IInstallHandler interface) are dynamically | ||
| 292 : | invoked as part of the installation process to handle non-plugin data, plus | ||
| 293 : | perform other custom processing allowed by the framework.</li> | ||
| 294 : | |||
| 295 : | celek | 1.7 | </ul> |
| 296 : | celek | 1.9 | Eclipse provides default implementations of feature and site. These are |
| 297 : | described in the rest of this document. <br> | ||
| 298 : | | ||
| 299 : | celek | 1.7 | <table border="1" cols="1" width="100%"> |
| 300 : | celek | 1.9 | <tbody> |
| 301 : | <tr> | ||
| 302 : | <td><b>Note: <i>The reminder of this document describes the default concrete | ||
| 303 : | implementation of the framework delivered with Eclipse. It specifies the | ||
| 304 : | structure of the default feature implementation, as well as the default site | ||
| 305 : | implementation, plus the corresponding xml files (feature.xml and site.xml). | ||
| 306 : | Providers of alternate concrete implementations can extend parts or | ||
| 307 : | all of the default Eclipse implementation. This includes providing a mechanism | ||
| 308 : | for dynamic computation of the site map (site.xml)</i></b></td> | ||
| 309 : | </tr> | ||
| 310 : | |||
| 311 : | </tbody> | ||
| 312 : | vlad | 1.1 | </table> |
| 313 : | celek | 1.9 | |
| 314 : | <h2> <a name="Packaging_Conventions"></a> Packaging Conventions</h2> | ||
| 315 : | Default feature packages consist of several related files: | ||
| 316 : | celek | 1.7 | <ul> |
| 317 : | celek | 1.9 | <li> exactly one jar containing the feature manifest and related files. |
| 318 : | celek | 1.7 | This one is refered to as the "<b>feature archive</b>"</li> |
| 319 : | celek | 1.9 | <li> zero or more jars containing the feature plug-ins. These are refered |
| 320 : | celek | 1.7 | to as the "<b>plug-in archives</b>"</li> |
| 321 : | celek | 1.9 | <li> zero or more non-plug-in files associated with the feature. They |
| 322 : | are used by feature custom install handlers and contain data not interpreted | ||
| 323 : | celek | 1.7 | by Eclipse</li> |
| 324 : | celek | 1.9 | |
| 325 : | </ul> | ||
| 326 : | |||
| 327 : | <h3> <a name="Feature_Archive"></a> Feature Archive</h3> | ||
| 328 : | The feature packaging information is placed into a separate Java .jar. | ||
| 329 : | Standard Java jar facilities are used for constructing feature archives. | ||
| 330 : | Feature archives reference separately packaged plug-in archives (see next | ||
| 331 : | section) and non-plug-in files. | ||
| 332 : | <p>Features are identified using a structured identifier based on the provider | ||
| 333 : | internet domain name. For example, organization eclipse.org may produce | ||
| 334 : | feature org.eclipse.javatooling. The character set used for feature identifiers | ||
| 335 : | is as specified for plug-in identifiers (see reference information describing | ||
| 336 : | the plug-in manifest). </p> | ||
| 337 : | celek | 1.7 | |
| 338 : | <p>The recommended convention for naming the feature archives is <br> | ||
| 339 : | celek | 1.9 | <tt><id>_<version>.jar</tt> </p> |
| 340 : | |||
| 341 : | <p>Where <tt><id></tt> is the feature identifier and <tt><version></tt> | ||
| 342 : | is the full version identifier contained in the respective feature.xml. | ||
| 343 : | Note that this is a recommended convention that minimizes chance of collisions, | ||
| 344 : | but is not required by the Eclipse architecture. For example, the following | ||
| 345 : | are valid feature archive names </p> | ||
| 346 : | |||
| 347 : | celek | 1.7 | <p><tt>org.eclipse.javatooling_1.0.3.jar</tt> <br> |
| 348 : | celek | 1.9 | <tt>org.eclipse.pde_2.0.jar</tt> <br> |
| 349 : | <tt>my_feature.jar</tt> </p> | ||
| 350 : | |||
| 351 : | <p>Internally, each feature archive is packaged relative to its feature directory | ||
| 352 : | (but not including the directory path element). The archive has the following | ||
| 353 : | celek | 1.7 | structure </p> |
| 354 : | celek | 1.9 | |
| 355 : | celek | 1.7 | <p><tt>feature.xml</tt> <br> |
| 356 : | celek | 1.9 | <tt>feature<_locale>.properties (see "Translated Feature Information")</tt> |
| 357 : | celek | 1.7 | <br> |
| 358 : | celek | 1.9 | <tt>other feature files and subdirectories (TBD)</tt> <br> |
| 359 : | <tt>META-INF/</tt> <br> | ||
| 360 : | <tt> Java jar manifest and security files</tt> </p> | ||
| 361 : | |||
| 362 : | celek | 1.7 | <p>The feature install.xml format is defined by the following dtd: </p> |
| 363 : | celek | 1.9 | |
| 364 : | celek | 1.7 | <p><tt><?xml encoding="ISO-8859-1"?></tt> </p> |
| 365 : | celek | 1.9 | |
| 366 : | <p><tt><!ELEMENT feature (install-handler?, description?, copyright?, | ||
| 367 : | license?, url?, includes*, requires?, plugin*, data*)></tt> <br> | ||
| 368 : | <tt><!ATTLIST feature</tt> <br> | ||
| 369 : | <tt> id | ||
| 370 : | CDATA #REQUIRED</tt> <br> | ||
| 371 : | <tt> version CDATA | ||
| 372 : | celek | 1.7 | #REQUIRED</tt> <br> |
| 373 : | celek | 1.9 | <tt> label |
| 374 : | CDATA #IMPLIED</tt> <br> | ||
| 375 : | <tt> provider-name CDATA #IMPLIED</tt> <br> | ||
| 376 : | <tt> image | ||
| 377 : | CDATA #IMPLIED</tt> <br> | ||
| 378 : | <tt> os | ||
| 379 : | CDATA #IMPLIED</tt> <br> | ||
| 380 : | <tt> arch | ||
| 381 : | CDATA #IMPLIED</tt> <br> | ||
| 382 : | <tt> ws | ||
| 383 : | CDATA #IMPLIED</tt> <br> | ||
| 384 : | <tt> nl | ||
| 385 : | CDATA #IMPLIED</tt> <br> | ||
| 386 : | <tt> colocation-affinity</tt> <br> | ||
| 387 : | <tt> | ||
| 388 : | CDATA #IMPLIED</tt> <br> | ||
| 389 : | <tt> primary (true | ||
| 390 : | celek | 1.7 | | false) "false"</tt> <br> |
| 391 : | celek | 1.9 | <tt> application CDATA #IMPLIED</tt> <br> |
| 392 : | <tt>></tt> </p> | ||
| 393 : | |||
| 394 : | celek | 1.7 | <p><tt><!ELEMENT install-handler EMPTY></tt> <br> |
| 395 : | celek | 1.9 | <tt><!ATTLIST install-handler</tt> <br> |
| 396 : | <tt> library CDATA | ||
| 397 : | celek | 1.7 | #IMPLIED</tt> <br> |
| 398 : | celek | 1.9 | <tt> handler CDATA |
| 399 : | celek | 1.7 | #IMPLIED</tt> <br> |
| 400 : | celek | 1.9 | <tt>></tt> </p> |
| 401 : | |||
| 402 : | celek | 1.7 | <p><tt><!ELEMENT description (#PCDATA)></tt> <br> |
| 403 : | celek | 1.9 | <tt><!ATTLIST description</tt> <br> |
| 404 : | <tt> url | ||
| 405 : | CDATA #IMPLIED</tt> <br> | ||
| 406 : | <tt>></tt> </p> | ||
| 407 : | |||
| 408 : | celek | 1.7 | <p><tt><!ELEMENT copyright (#PCDATA)></tt> <br> |
| 409 : | celek | 1.9 | <tt><!ATTLIST copyright</tt> <br> |
| 410 : | <tt> url | ||
| 411 : | CDATA #IMPLIED</tt> <br> | ||
| 412 : | <tt>></tt> </p> | ||
| 413 : | |||
| 414 : | celek | 1.7 | <p><tt><!ELEMENT license (#PCDATA)></tt> <br> |
| 415 : | celek | 1.9 | <tt><!ATTLIST license</tt> <br> |
| 416 : | <tt> url | ||
| 417 : | CDATA #IMPLIED</tt> <br> | ||
| 418 : | <tt>></tt> </p> | ||
| 419 : | |||
| 420 : | celek | 1.7 | <p><tt><!ELEMENT url (update?, discovery*)></tt> </p> |
| 421 : | celek | 1.9 | |
| 422 : | celek | 1.7 | <p><tt><!ELEMENT update EMPTY></tt> <br> |
| 423 : | celek | 1.9 | <tt><!ATTLIST update</tt> <br> |
| 424 : | <tt> url | ||
| 425 : | CDATA #REQUIRED</tt> <br> | ||
| 426 : | <tt> label | ||
| 427 : | CDATA #IMPLIED</tt> <br> | ||
| 428 : | <tt>></tt> </p> | ||
| 429 : | |||
| 430 : | celek | 1.7 | <p><tt><!ELEMENT discovery EMPTY></tt> <br> |
| 431 : | celek | 1.9 | <tt><!ATTLIST discovery</tt> <br> |
| 432 : | <tt> url | ||
| 433 : | CDATA #REQUIRED</tt> <br> | ||
| 434 : | <tt> label | ||
| 435 : | CDATA #IMPLIED</tt> <br> | ||
| 436 : | <tt>></tt> </p> | ||
| 437 : | |||
| 438 : | celek | 1.7 | <p><tt><!ELEMENT includes EMPTY></tt> <br> |
| 439 : | celek | 1.9 | <tt><!ATTLIST includes</tt> <br> |
| 440 : | <tt> id | ||
| 441 : | CDATA #REQUIRED</tt> <br> | ||
| 442 : | <tt> version | ||
| 443 : | celek | 1.7 | CDATA #REQUIRED</tt> <br> |
| 444 : | celek | 1.9 | <tt> name |
| 445 : | CDATA #IMPLIED</tt> <br> | ||
| 446 : | <tt> optional </tt><tt> | ||
| 447 : | celek | 1.7 | (true | false) "false"</tt><tt> <br> |
| 448 : | celek | 1.9 | </tt><tt> match |
| 449 : | (perfect | equivalent | compatible | greaterOrEqual) | ||
| 450 : | "compatible"</tt><tt> </tt><br> | ||
| 451 : | <tt> search_location </tt><tt>(</tt><font | ||
| 452 : | color="#000000"><tt> root | self | both) "root"</tt></font><br> | ||
| 453 : | <tt>></tt> </p> | ||
| 454 : | |||
| 455 : | celek | 1.7 | <p><tt><!ELEMENT requires (import+)></tt> </p> |
| 456 : | celek | 1.9 | |
| 457 : | celek | 1.7 | <p><tt><!ELEMENT import EMPTY></tt> <br> |
| 458 : | celek | 1.9 | <tt><!ATTLIST import</tt> <br> |
| 459 : | <tt> plugin | ||
| 460 : | CDATA #IMPLIED</tt><br> | ||
| 461 : | <tt> feature CDATA #IMPLIED</tt><br> | ||
| 462 : | <tt> version CDATA | ||
| 463 : | celek | 1.7 | #IMPLIED</tt> <br> |
| 464 : | celek | 1.9 | <tt> match (perfect |
| 465 : | celek | 1.8 | | equivalent | compatible | greaterOrEqual) "compatible"</tt> <br> |
| 466 : | celek | 1.9 | <tt> patch </tt><tt> |
| 467 : | celek | 1.8 | (true | false) "false"</tt><tt> </tt><tt><br> |
| 468 : | celek | 1.9 | ></tt><br> |
| 469 : | </p> | ||
| 470 : | |||
| 471 : | celek | 1.7 | <p><tt><!ELEMENT plugin EMPTY></tt> <br> |
| 472 : | celek | 1.9 | <tt><!ATTLIST plugin</tt> <br> |
| 473 : | <tt> id | ||
| 474 : | CDATA #REQUIRED</tt> <br> | ||
| 475 : | <tt> version CDATA | ||
| 476 : | celek | 1.7 | #REQUIRED</tt> <br> |
| 477 : | celek | 1.9 | <tt> fragment (true | false) |
| 478 : | celek | 1.7 | "false"</tt> <br> |
| 479 : | celek | 1.9 | <tt> os |
| 480 : | CDATA #IMPLIED</tt> <br> | ||
| 481 : | <tt> arch | ||
| 482 : | CDATA #IMPLIED</tt> <br> | ||
| 483 : | <tt> ws | ||
| 484 : | CDATA #IMPLIED</tt> <br> | ||
| 485 : | <tt> nl | ||
| 486 : | CDATA #IMPLIED</tt> <br> | ||
| 487 : | <tt> download-size CDATA #IMPLIED</tt> <br> | ||
| 488 : | <tt> install-size CDATA #IMPLIED</tt> <br> | ||
| 489 : | <tt>></tt> </p> | ||
| 490 : | |||
| 491 : | celek | 1.7 | <p><tt><!ELEMENT data EMPTY></tt> <br> |
| 492 : | celek | 1.9 | <tt><!ATTLIST data</tt> <br> |
| 493 : | <tt> id | ||
| 494 : | CDATA #REQUIRED</tt> <br> | ||
| 495 : | <tt> os | ||
| 496 : | CDATA #IMPLIED</tt> <br> | ||
| 497 : | <tt> arch | ||
| 498 : | CDATA #IMPLIED</tt> <br> | ||
| 499 : | <tt> ws | ||
| 500 : | CDATA #IMPLIED</tt> <br> | ||
| 501 : | <tt> nl | ||
| 502 : | CDATA #IMPLIED</tt> <br> | ||
| 503 : | <tt> download-size CDATA #IMPLIED</tt> <br> | ||
| 504 : | <tt> install-size CDATA #IMPLIED</tt> <br> | ||
| 505 : | <tt>></tt> </p> | ||
| 506 : | |||
| 507 : | celek | 1.7 | <p>The element and attribute definitions are as follows: </p> |
| 508 : | celek | 1.9 | |
| 509 : | celek | 1.7 | <ul> |
| 510 : | celek | 1.9 | <li> <feature> - defines the feature</li> |
| 511 : | |||
| 512 : | celek | 1.7 | <ul> |
| 513 : | celek | 1.9 | <li> id - required feature identifier (eg. com.xyz.myfeature)</li> |
| 514 : | <li> version - required component version (eg. 1.0.3)</li> | ||
| 515 : | <li> label - optional displayable label (name). Intended to be translated.</li> | ||
| 516 : | <li> provider-name - optional display label identifying the organization | ||
| 517 : | celek | 1.7 | providing this component. Intended to be translated.</li> |
| 518 : | celek | 1.9 | <li> image - optional image to use when displaying information about the |
| 519 : | celek | 1.7 | feature. Specified relative to the feature.xml.</li> |
| 520 : | celek | 1.9 | <li> os - optional operating system specification. A comma-separated list |
| 521 : | of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 522 : | . Indicates this feature should only be installed on one of the specified | ||
| 523 : | os systems. If this attribute is not specified, the feature can be installed | ||
| 524 : | on all systems (portable implementation). This information is used as a | ||
| 525 : | hint by the installation and update support (user can force installation | ||
| 526 : | of feature regardless of this setting).</li> | ||
| 527 : | <li> arch - optional machine architecture specification. A comma-separated | ||
| 528 : | list of architecture designators defined by Eclipse (see Javadoc for <tt> | ||
| 529 : | org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only | ||
| 530 : | be installed on one of the specified systems. If this attribute is not specified, | ||
| 531 : | the feature can be installed on all systems (portable implementation). This | ||
| 532 : | information is used as a hint by the installation and update support (user | ||
| 533 : | celek | 1.7 | can force installation of feature regardless of this setting).</li> |
| 534 : | celek | 1.9 | <li> ws - optional windowing system specification. A comma-separated list |
| 535 : | of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 536 : | . Indicates this feature should only be installed on one of the specified | ||
| 537 : | ws systems. If this attribute is not specified, the feature can be installed | ||
| 538 : | on all systems (portable implementation). This information is used as a | ||
| 539 : | hint by the installation and update support (user can force installation | ||
| 540 : | of feature regardless of this setting).</li> | ||
| 541 : | <li> nl - optional locale specification. A comma-separated list of locale | ||
| 542 : | designators defined by Java. Indicates this feature should only be installed | ||
| 543 : | on a system running with a compatible locale (using Java locale-matching rules). | ||
| 544 : | If this attribute is not specified, the feature can be installed on all systems | ||
| 545 : | (language-neutral implementation). This information is used as a hint by | ||
| 546 : | the installation and update support (user can force installation of feature | ||
| 547 : | celek | 1.7 | regardless of this setting).</li> |
| 548 : | celek | 1.9 | <li> colocation-affinity - optional reference to another feature identifier |
| 549 : | used to select the default installation location for this feature. When | ||
| 550 : | this feature is being installed as a new feature (no other versions of it | ||
| 551 : | are installed), an attempt is made to install this feature in the same installation | ||
| 552 : | celek | 1.7 | location as the referenced feature.</li> |
| 553 : | celek | 1.9 | <li> primary - optional indication specifying whether this feature can |
| 554 : | be used as a <a href="#Dominant_Feature">primary feature</a> . Default if | ||
| 555 : | <i>false</i> (not a primary feature).</li> | ||
| 556 : | <li> application - optional identifier of the Eclipse application that | ||
| 557 : | is to be used during startup when the declaring feature is the <a | ||
| 558 : | href="#Dominant_Feature"> primary feature</a> . The application identifier | ||
| 559 : | must represent a valid application registered in the <tt>org.eclipse.core.runtime.applications</tt> | ||
| 560 : | extension point. Default is <tt>org.eclipse.ui.workbench</tt>.</li> | ||
| 561 : | |||
| 562 : | </ul> | ||
| 563 : | <li> <install-handler></li> | ||
| 564 : | |||
| 565 : | <ul> | ||
| 566 : | <li> library - optional .jar library containing the install handler classes. | ||
| 567 : | If specified, the referenced .jar must be contained in the feature archive. | ||
| 568 : | It is specified as a path within the feature archive, relative to the feature.xml | ||
| 569 : | entry. If not specified, the feature archive itself is used to load the | ||
| 570 : | install handler classes. This attribute is only interpreted if <i>class</i> | ||
| 571 : | attribute is also specified</li> | ||
| 572 : | <li> handler - optional identifier of the install handler. The value is | ||
| 573 : | interpreted depending on the value of the <i>library</i> attribute. If <i> | ||
| 574 : | library</i> is specified, the value is interpreted as a fully qualified | ||
| 575 : | name of a class contained in the specified <i>library</i>. If <i>library</i> | ||
| 576 : | is not specified, the value is is interpreted as an extension identifier | ||
| 577 : | of an extension registered in the <i>org.eclipse.update.installHandlers</i> | ||
| 578 : | extension point. In either case, the resulting class must implement the | ||
| 579 : | <i> IInstallHandler</i> interface. The class is dynamically loaded | ||
| 580 : | and called at specific points during feature processing. The handler has | ||
| 581 : | visibility to the API classes from the update plug-in, and Eclipse plug-ins | ||
| 582 : | required by the update plugin.</li> | ||
| 583 : | |||
| 584 : | celek | 1.7 | </ul> |
| 585 : | celek | 1.9 | <li> <description> - brief component description as simple text. |
| 586 : | celek | 1.7 | Intended to be translated.</li> |
| 587 : | celek | 1.9 | |
| 588 : | celek | 1.7 | <ul> |
| 589 : | celek | 1.9 | <li> url - optional URL for the full description as HTML. The URL can be |
| 590 : | specified as absolute of relative. If relative, it is assumed to be relative | ||
| 591 : | to (and packaged in) the feature archive. Note, that for NL handling the URL | ||
| 592 : | value should be separated to allow alternate URLs to be specified for each | ||
| 593 : | national language.</li> | ||
| 594 : | |||
| 595 : | celek | 1.7 | </ul> |
| 596 : | celek | 1.9 | <li> <copyright> - feature copyright as simple text. Intended to |
| 597 : | celek | 1.7 | be translated.</li> |
| 598 : | celek | 1.9 | |
| 599 : | celek | 1.7 | <ul> |
| 600 : | celek | 1.9 | <li> url - optional URL for the full description as HTML. The URL can be |
| 601 : | specified as absolute of relative. If relative, it is assumed to be relative | ||
| 602 : | to (and packaged in) the feature archive. Note, that for NL handling the URL | ||
| 603 : | value should be separated to allow alternate URLs to be specified for each | ||
| 604 : | national language.</li> | ||
| 605 : | |||
| 606 : | </ul> | ||
| 607 : | <li> <license> - feature "click-through" license as simple text. | ||
| 608 : | Intended to be translated. It is displayed in a standard dialog with [Accept] | ||
| 609 : | [Reject] actions during the download/ installation process. Note, that click-through | ||
| 610 : | license must be specified for any feature that will be selected for installation | ||
| 611 : | or update using the Eclipse update manager. When using nested features, | ||
| 612 : | only the nesting parent (ie. the feature selected for installation or update) | ||
| 613 : | must have click-through license text defined. The license text is required | ||
| 614 : | even if the optional <i>url</i> attribute is specified.</li> | ||
| 615 : | |||
| 616 : | <ul> | ||
| 617 : | <li> url - optional URL for the full description as HTML. The URL can be | ||
| 618 : | specified as absolute of relative. If relative, it is assumed to be relative | ||
| 619 : | to (and packaged in) the feature archive. Note, that for NL handling the URL | ||
| 620 : | value should be separated to allow alternate URLs to be specified for each | ||
| 621 : | national language. Note, that the "content" of this URL is <b>not</b> what | ||
| 622 : | is presented as the click-through license during installation processing. | ||
| 623 : | The click-through license is the actual value of the <i><license></i> | ||
| 624 : | celek | 1.7 | element (eg. <tt><license>click through text</license></tt>)</li> |
| 625 : | celek | 1.9 | |
| 626 : | celek | 1.7 | </ul> |
| 627 : | celek | 1.9 | <li> <url> - optional URL specifying site(s) contain feature updates, |
| 628 : | celek | 1.7 | or new features</li> |
| 629 : | celek | 1.9 | |
| 630 : | celek | 1.7 | <ul> |
| 631 : | celek | 1.9 | <li> <update> - URL to go to for updates to this feature</li> |
| 632 : | |||
| 633 : | celek | 1.7 | <ul> |
| 634 : | celek | 1.9 | <li> url - actual URL</li> |
| 635 : | <li> label - displayable label (name) for the referenced site</li> | ||
| 636 : | |||
| 637 : | celek | 1.7 | </ul> |
| 638 : | celek | 1.9 | <li> <discovery> - URL to go to for new features. In general, a |
| 639 : | provider can use this element to reference its own site(s), or site(s) of | ||
| 640 : | partners that offer complementary features. Eclipse uses this element simply | ||
| 641 : | as a way to distribute new site URLs to the clients</li> | ||
| 642 : | |||
| 643 : | celek | 1.7 | <ul> |
| 644 : | celek | 1.9 | <li> url - actual URL</li> |
| 645 : | <li> label - displayable label (name) for the referenced site</li> | ||
| 646 : | |||
| 647 : | celek | 1.7 | </ul> |
| 648 : | celek | 1.9 | |
| 649 : | celek | 1.7 | </ul> |
| 650 : | celek | 1.9 | <li> <includes> - optional reference to a nested feature that is |
| 651 : | considered to be part of this feature. Nested features must be located on | ||
| 652 : | celek | 1.7 | the same update site as this feature</li> |
| 653 : | celek | 1.9 | |
| 654 : | celek | 1.7 | <ul> |
| 655 : | celek | 1.9 | <li> id - required nested feature identifier</li> |
| 656 : | <li> version - required nested feature version</li> | ||
| 657 : | <li> name- optional displayable label (name). Intended to be translated.</li> | ||
| 658 : | <li>optional - optional specification indicating if this included feature | ||
| 659 : | celek | 1.8 | can be optionally installed. Default is "false"<br> |
| 660 : | celek | 1.9 | </li> |
| 661 : | <li>match - optional rule that will be applied when resolving | ||
| 662 : | the feature reference. A <samp>perfect</samp> match (the default that matches | ||
| 663 : | the 2.0.1 behavior) requires that the feature has exactly the version specified | ||
| 664 : | by the version attribute. Other choices progressively relax the rule (<samp> | ||
| 665 : | equivalent</samp> allows only service part of the version to be more recent, | ||
| 666 : | <samp>compatible</samp> also allows minor part to be included in the | ||
| 667 : | consideration, while <samp>greaterOrEqual</samp> simply allows any version | ||
| 668 : | celek | 1.8 | that is more recent or identical to the one specified).</li> |
| 669 : | celek | 1.9 | <li>search_location - optional. Indicates whether the "New Updates" |
| 670 : | action should search the update location determined by the nesting root feature | ||
| 671 : | (<tt>root</tt>, is the default), or the location defined by the nested feature | ||
| 672 : | (<tt>self</tt>), or search both (<tt>both</tt>) in that order (root first, | ||
| 673 : | celek | 1.8 | self if nothing is found).</li> |
| 674 : | celek | 1.9 | |
| 675 : | celek | 1.7 | </ul> |
| 676 : | celek | 1.9 | <li> <requires> - optional feature dependency information. Is expressed |
| 677 : | in terms of plug-in dependencies. If specified, is enforced by the installation | ||
| 678 : | and update support at the time of installation</li> | ||
| 679 : | |||
| 680 : | celek | 1.7 | <ul> |
| 681 : | celek | 1.9 | <li> <import> - dependency entry. Specification and processing is |
| 682 : | celek | 1.7 | a subset of the <import> specification in plugin.xml</li> |
| 683 : | celek | 1.9 | |
| 684 : | celek | 1.7 | <ul> |
| 685 : | celek | 1.9 | <li> plugin - identifier of dependent plug-in.</li> |
| 686 : | <li> feature - identifier of dependent feature. If plugin and feature | ||
| 687 : | are specified, plugin takes precedence upon feature. Feature or plugin must | ||
| 688 : | celek | 1.8 | be specified.</li> |
| 689 : | celek | 1.9 | <li> version - optional plug-in/feature version specification</li> |
| 690 : | <li>patch - optional specification indicating if this feature is a | ||
| 691 : | patch of the dependant feature. Default is "false". If patch is true, version | ||
| 692 : | must be specified. If patch is true, only feature must be specified. If patch | ||
| 693 : | celek | 1.8 | is true, and match is specified, it must be 'perfect'.<br> |
| 694 : | celek | 1.9 | </li> |
| 695 : | <li> match - optional matching rule. Valid values and processing are as | ||
| 696 : | celek | 1.7 | follows:</li> |
| 697 : | celek | 1.9 | |
| 698 : | celek | 1.7 | <ul> |
| 699 : | celek | 1.9 | <li> if version attribute is not specified, the match attribute (if specified) |
| 700 : | is ignored.</li> | ||
| 701 : | <li>if version is specified, match defaults to compatible.<br> | ||
| 702 : | </li> | ||
| 703 : | <li>if patch is true, and match is not specified, match defaults | ||
| 704 : | celek | 1.8 | to perfect.<br> |
| 705 : | celek | 1.9 | </li> |
| 706 : | <li> <b><i>perfect</i></b> - dependent plug-in version must match exactly | ||
| 707 : | celek | 1.7 | the specified version.</li> |
| 708 : | celek | 1.9 | <li> <b><i>equivalent</i></b> - dependent plug-in version must be at least |
| 709 : | at the version specified, or at a higher service level (major and minor version | ||
| 710 : | levels must equal the specified version).</li> | ||
| 711 : | <li> <b><i>compatible</i></b> - dependent plug-in version must be at least | ||
| 712 : | at the version specified, or at a higher service level or minor level (major | ||
| 713 : | version level must equal the specified version).</li> | ||
| 714 : | <li> <b><i>greaterOrEqual</i></b> - dependent plug-in version must be | ||
| 715 : | at least at the version specified, or at a higher service, minor or major | ||
| 716 : | level.</li> | ||
| 717 : | |||
| 718 : | celek | 1.7 | </ul> |
| 719 : | celek | 1.9 | |
| 720 : | celek | 1.7 | </ul> |
| 721 : | celek | 1.9 | |
| 722 : | celek | 1.7 | </ul> |
| 723 : | celek | 1.9 | <li> <plugin> - identifies referenced plug-in</li> |
| 724 : | |||
| 725 : | celek | 1.7 | <ul> |
| 726 : | celek | 1.9 | <li> id - required plug-in identifier (from plugin.xml)</li> |
| 727 : | <li> version - required plug-in version (from plugin.xml)</li> | ||
| 728 : | <li> fragment - optional specification indicating if this entry is a plug-in | ||
| 729 : | fragment. Default is "false"</li> | ||
| 730 : | <li> os - optional operating system specification. A comma-separated list | ||
| 731 : | of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 732 : | . Indicates this entry should only be installed on one of the specified os | ||
| 733 : | systems. If this attribute is not specified, the entry can be installed | ||
| 734 : | on all systems (portable implementation). This information is used as a hint | ||
| 735 : | by the installation and update support (user can force installation of entry | ||
| 736 : | celek | 1.7 | regardless of this setting).</li> |
| 737 : | celek | 1.9 | <li> arch - optional machine architecture specification. A comma-separated |
| 738 : | list of architecture designators defined by Eclipse (see Javadoc for <tt> | ||
| 739 : | org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only | ||
| 740 : | be installed on one of the specified systems. If this attribute is not specified, | ||
| 741 : | the feature can be installed on all systems (portable implementation). This | ||
| 742 : | information is used as a hint by the installation and update support (user | ||
| 743 : | celek | 1.7 | can force installation of feature regardless of this setting).</li> |
| 744 : | celek | 1.9 | <li> ws - optional windowing system specification. A comma-separated list |
| 745 : | of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 746 : | . Indicates this entry should only be installed on one of the specified ws | ||
| 747 : | systems. If this attribute is not specified, the entry can be installed | ||
| 748 : | on all systems (portable implementation). This information is used as a hint | ||
| 749 : | by the installation and update support (user can force installation of entry | ||
| 750 : | celek | 1.7 | regardless of this setting).</li> |
| 751 : | celek | 1.9 | <li> nl - optional locale specification. A comma-separated list of locale |
| 752 : | designators defined by Java. Indicates this entry should only be installed | ||
| 753 : | on a system running with a compatible locale (using Java locale-matching rules). | ||
| 754 : | If this attribute is not specified, the entry can be installed on all systems | ||
| 755 : | (language-neutral implementation). This information is used as a hint by | ||
| 756 : | the installation and update support (user can force installation of entry | ||
| 757 : | regardless of this setting).</li> | ||
| 758 : | <li> download-size - optional hint supplied by the feature packager, indicating | ||
| 759 : | the download size in KBytes of the referenced plug-in archive. If not specified, | ||
| 760 : | the download size is not known (<b>Implementation Note:</b> the implementation | ||
| 761 : | needs to distinguish between "not known" and 0 size)</li> | ||
| 762 : | <li> install-size - optional hint supplied by the feature packager, indicating | ||
| 763 : | the install size in KBytes of the referenced plug-in archive. If not specified, | ||
| 764 : | the install size is not known (<b>Implementation Note:</b> the implementation | ||
| 765 : | needs to distinguish between "not known" and 0 size)</li> | ||
| 766 : | |||
| 767 : | </ul> | ||
| 768 : | <li> <data> - identifies non-plugin data that is part of the feature</li> | ||
| 769 : | |||
| 770 : | <ul> | ||
| 771 : | <li> id - required data identifier in the form of a relative path.</li> | ||
| 772 : | <li> os - optional operating system specification. A comma-separated list | ||
| 773 : | of os designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 774 : | . Indicates this entry should only be installed on one of the specified os | ||
| 775 : | systems. If this attribute is not specified, the entry can be installed | ||
| 776 : | on all systems (portable implementation). This information is used as a hint | ||
| 777 : | by the installation and update support (user can force installation of entry | ||
| 778 : | celek | 1.7 | regardless of this setting).</li> |
| 779 : | celek | 1.9 | <li> arch - optional machine architecture specification. A comma-separated |
| 780 : | list of architecture designators defined by Eclipse (see Javadoc for <tt> | ||
| 781 : | org.eclipse.core.boot.BootLoader)</tt>. Indicates this feature should only | ||
| 782 : | be installed on one of the specified systems. If this attribute is not specified, | ||
| 783 : | the feature can be installed on all systems (portable implementation). This | ||
| 784 : | information is used as a hint by the installation and update support (user | ||
| 785 : | celek | 1.7 | can force installation of feature regardless of this setting).</li> |
| 786 : | celek | 1.9 | <li> ws - optional windowing system specification. A comma-separated list |
| 787 : | of ws designators defined by Eclipse (see Javadoc for <tt>org.eclipse.core.boot.BootLoader)</tt> | ||
| 788 : | . Indicates this entry should only be installed on one of the specified ws | ||
| 789 : | systems. If this attribute is not specified, the entry can be installed | ||
| 790 : | on all systems (portable implementation). This information is used as a hint | ||
| 791 : | by the installation and update support (user can force installation of entry | ||
| 792 : | regardless of this setting).</li> | ||
| 793 : | <li> nl - optional locale specification. A comma-separated list of locale | ||
| 794 : | designators defined by Java. Indicates this entry should only be installed | ||
| 795 : | on a system running with a compatible locale (using Java locale-matching rules). | ||
| 796 : | If this attribute is not specified, the entry can be installed on all systems | ||
| 797 : | (language-neutral implementation). This information is used as a hint by | ||
| 798 : | the installation and update support (user can force installation of entry | ||
| 799 : | celek | 1.7 | regardless of this setting).</li> |
| 800 : | celek | 1.9 | <li> download-size - optional hint supplied by the feature packager, indicating |
| 801 : | the download size in KBytes of the referenced data archive. If not specified, | ||
| 802 : | the download size is not known (<b>Implementation Note:</b> the implementation | ||
| 803 : | needs to distinguish between "not known" and 0 size)</li> | ||
| 804 : | <li> install-size - optional hint supplied by the feature packager, indicating | ||
| 805 : | the install size in KBytes of the referenced data archive. If not specified, | ||
| 806 : | the install size is not known (<b>Implementation Note:</b> the implementation | ||
| 807 : | needs to distinguish between "not known" and 0 size)</li> | ||
| 808 : | |||
| 809 : | celek | 1.7 | </ul> |
| 810 : | celek | 1.9 | |
| 811 : | </ul> | ||
| 812 : | <a name="Feature_Archive_Mapping_Id_To_Path"></a> When interacting with | ||
| 813 : | the update site, the feature implementation maps the <tt><plugin></tt> | ||
| 814 : | and <tt><data></tt> elements into path identifiers used by the site | ||
| 815 : | to determine the actual files to download and install. The default feature | ||
| 816 : | implementation supplied by Eclipse constructs the path identifiers as follows: | ||
| 817 : | celek | 1.7 | |
| 818 : | <ul> | ||
| 819 : | celek | 1.9 | <li> <tt><plugin></tt> element results in a path entry in the form |
| 820 : | "<tt>plugins/<pluginId>_<pluginVersion>.jar</tt>" (for example, | ||
| 821 : | celek | 1.7 | "<tt>plugins/org.eclipse.core.boot_1.0.3.jar</tt>")</li> |
| 822 : | celek | 1.9 | <li> <tt><data></tt> element results in a path entry in the form |
| 823 : | "<tt>features/<featureId>_<featureVersion>/<dataId></tt> | ||
| 824 : | celek | 1.7 | " (for example, "f<tt>eatures/com.xyz.tools_2.3.1/examples.zip</tt>")</li> |
| 825 : | celek | 1.9 | |
| 826 : | celek | 1.7 | </ul> |
| 827 : | celek | 1.9 | Note, that in general the feature.xml manifest documents should specify |
| 828 : | UTF-8 encoding. For example | ||
| 829 : | celek | 1.7 | <p><tt><?xml version="1.0" encoding="UTF-8"?></tt> </p> |
| 830 : | celek | 1.9 | |
| 831 : | <p>Translatable text contained in the feature.xml can be separated into feature<_locale>.properties | ||
| 832 : | files using Java property bundle conventions. Note that the translated strings | ||
| 833 : | are used at installation time (ie. do not employ the plug-in fragment runtime | ||
| 834 : | celek | 1.7 | mechanism). </p> |
| 835 : | celek | 1.9 | |
| 836 : | <h3> <a name="Plug-In_Archive"></a> Plug-In Archive</h3> | ||
| 837 : | Plug-ins and plug-in fragments are individually packaged as separate Java | ||
| 838 : | .jars. Standard Java jar facilities are used for constructing plug-in archives. | ||
| 839 : | There is no distinction made between a plug-in archive containing a plug-in | ||
| 840 : | and one containing a plug-in fragment. | ||
| 841 : | celek | 1.7 | <p>The recommended convention for naming the plug-in archives is <br> |
| 842 : | celek | 1.9 | <tt><id>_<version>.jar</tt> </p> |
| 843 : | |||
| 844 : | <p>Where <tt><id></tt> is the plug-in or fragment identifier and <tt> | ||
| 845 : | <version></tt> is the full version identifier contained in the respective | ||
| 846 : | plugin.xml or fragment.xml. Note that this is a recommended convention that | ||
| 847 : | minimizes chance of collisions, but is not required by the Eclipse architecture. | ||
| 848 : | For example, the following are valid plug-in archive names </p> | ||
| 849 : | |||
| 850 : | celek | 1.7 | <p><tt>org.eclipse.platform_1.0.3.jar</tt> <br> |
| 851 : | celek | 1.9 | <tt>org.eclipse.ui.nl_2.0.jar</tt> <br> |
| 852 : | <tt>my_plugin.jar</tt> </p> | ||
| 853 : | |||
| 854 : | <p>Internally, each plug-in archive packages all the relevant plug-in or | ||
| 855 : | fragment files relative to its plug-in or fragment directory (but not including | ||
| 856 : | the directory path element). The archive has the following structure </p> | ||
| 857 : | |||
| 858 : | celek | 1.7 | <p><tt>plugin.xml *OR* fragment.xml</tt> <br> |
| 859 : | celek | 1.9 | <tt>other plug-in or feature files and subdirectories</tt> <br> |
| 860 : | <tt>META-INF/</tt> <br> | ||
| 861 : | <tt> Java jar manifest and security files</tt> </p> | ||
| 862 : | |||
| 863 : | <h3> <a name="Packaging_NL"></a> Packaging NL</h3> | ||
| 864 : | In Eclipse, translated plug-in information is packaged either together | ||
| 865 : | with the base plug-in, or as a plug-in fragment. At runtime, Eclipse locates | ||
| 866 : | the translations for the required locale. The use of fragments allows translations | ||
| 867 : | to be added to the runtime without the need to repackage the base plug-ins. | ||
| 868 : | |||
| 869 : | <p>This mechanism cannot be used for translating the actual packaging information | ||
| 870 : | that is part of the installation xml files. Consequently the standard Java | ||
| 871 : | translation conventions are used for the packaging information, and all | ||
| 872 : | necessary translations must be available at the time the feature is packaged. | ||
| 873 : | </p> | ||
| 874 : | |||
| 875 : | <h4> <a name="Translated_Feature_Information"></a> Translated Feature Information</h4> | ||
| 876 : | <b>Note:</b> This section describes the conventions used for translating | ||
| 877 : | the information contained within the feature manifest. It allows for the | ||
| 878 : | update client to select the correctly localized strings from the update server. | ||
| 879 : | This section specifically does not describe localization of individual plug-ins. | ||
| 880 : | |||
| 881 : | <p>Several of the attributes within the feature manifest are strings intended | ||
| 882 : | for display through user interfaces. To facilitate translation, these attribute | ||
| 883 : | values use the convention defined for translatable attributes of plugin.xml. | ||
| 884 : | Strings beginning with % up to the first space are treated as resource identifier | ||
| 885 : | celek | 1.7 | keys (without the %) and looked up in a properties file. For example </p> |
| 886 : | celek | 1.9 | |
| 887 : | celek | 1.7 | <p><tt>label="%cfg Tool Feature for Linux"</tt> </p> |
| 888 : | celek | 1.9 | |
| 889 : | <p>results in a resource lookup in the correct property file with key "cfg". | ||
| 890 : | If no property files are supplied, or the key is not found the default string | ||
| 891 : | celek | 1.7 | value (following the %key) is used. </p> |
| 892 : | celek | 1.9 | |
| 893 : | <p>The property files are named as feature_<locale>.properties using | ||
| 894 : | the Java resource bundle naming conventions. Within the feature archive | ||
| 895 : | .jar they are placed in the same directory as their corresponding feature.xml | ||
| 896 : | file. </p> | ||
| 897 : | |||
| 898 : | <p><b>Implementation Note</b>: When accessing the resource bundles the Eclipse | ||
| 899 : | installation and update code should create a class loader for accessing the | ||
| 900 : | translated string. This way, the standard locale lookup algorithm implemented | ||
| 901 : | by Java is automatically used. </p> | ||
| 902 : | |||
| 903 : | celek | 1.7 | <p><tt>ResourceBundle b;</tt> <br> |
| 904 : | celek | 1.9 | <tt>ClassLoader l;</tt> <br> |
| 905 : | <tt>l = new URLClassLoader(new URL[] {<targetDirectoryURL>}, null);</tt> | ||
| 906 : | celek | 1.7 | <br> |
| 907 : | celek | 1.9 | <tt>b = ResourceBundle.getBundle("feature",Locale.getDefault(),l);</tt> |
| 908 : | celek | 1.7 | </p> |
| 909 : | celek | 1.9 | |
| 910 : | <p>The resulting resource bundle can be used in <tt>IPluginDescriptor.getResourceString(String,ResourceBundle)</tt> | ||
| 911 : | to actually return the correct translated string for the manifest attribute. | ||
| 912 : | </p> | ||
| 913 : | |||
| 914 : | <h4> <a name="Translated_Plug-In_Information"></a> Translated Plug-In Information</h4> | ||
| 915 : | No change from 1.0. Translated plug-in information should be packaged as | ||
| 916 : | plug-in fragments. | ||
| 917 : | <h3> <a name="Packaging_Target-Specific_Support"></a> Packaging Target-Specific | ||
| 918 : | Support</h3> | ||
| 919 : | No change from 1.0. Target-specific plug-in support (os, ws) should be | ||
| 920 : | packaged as plug-in fragments. | ||
| 921 : | <h3> <a name="Packaging_Attribution_Information"></a> Packaging Attribution | ||
| 922 : | Information</h3> | ||
| 923 : | This topic is covered in separate documents available on the eclipse.org | ||
| 924 : | development resources page of the Update component. | ||
| 925 : | <h3> <a name="Packaging_Non_Plug_In_Files"></a> Packaging Non-Plug-In Files</h3> | ||
| 926 : | Arbitrary non-plug-in files can be included as part of the feature definition | ||
| 927 : | using the <tt><data></tt> elements. Non-plug-in files typically also | ||
| 928 : | requires specification of a custom install handler. In general, the Eclipse | ||
| 929 : | support only downloads the referenced non-plug-in files and calls the custom | ||
| 930 : | install handler to perform any actual installation steps. | ||
| 931 : | celek | 1.7 | <p>Eclipse does not specify the format of the non-plug-in files. </p> |
| 932 : | celek | 1.9 | |
| 933 : | <h3> <a name="Custom_Install_Handling"></a> Custom Install Handling</h3> | ||
| 934 : | Custom install handlers are written as a Java class and are packaged as | ||
| 935 : | part of the <a href="#Feature_Archive">feature archive</a> . The installer | ||
| 936 : | must implement the <tt>IInstallHandler</tt> interface (in most cases will | ||
| 937 : | extend the <tt>BaseInstallHandler</tt> abstract helper class which implements | ||
| 938 : | <tt>IInstallHandler</tt>). When required, the install handler is dynamically | ||
| 939 : | loaded by the installation and update code, and is called at specific points | ||
| 940 : | during its processing. The install handler code has visibility to classes | ||
| 941 : | from the installation and update support plug-in, and its prerequisite plug-ins. | ||
| 942 : | |||
| 943 : | <p><b>Implementation Note:</b> the detailed list of visible prerequisite | ||
| 944 : | plug-ins is still evolving. It is expected to include <tt>org.eclipse.core.boot | ||
| 945 : | </tt> and <tt>org.eclipse.core.runtime</tt> in all cases, plus <tt>org.eclipse.ui</tt> | ||
| 946 : | and <tt>org.eclipse.swt</tt> when running with full workbench (ie. not "headless | ||
| 947 : | mode"). Also, it would be useful to always expose <tt>org.eclipse.core.ant</tt> | ||
| 948 : | so that build scripts can be used as part of the install handler implementation. | ||
| 949 : | </p> | ||
| 950 : | |||
| 951 : | <p>The IInstallHandler interface supports the following methods [<b>Implementation | ||
| 952 : | Note:</b> the detailed definition of the IInstallHandler interface is still | ||
| 953 : | evolving. The description below is not an API specification (simply a functional | ||
| 954 : | description)]: </p> | ||
| 955 : | |||
| 956 : | celek | 1.7 | <ul> |
| 957 : | celek | 1.9 | <li> install-initiated - the install handler is called after a feature |
| 958 : | was selected for installation, but before any files were downloaded. It is | ||
| 959 : | intended to implement any custom click-through or user registration dialogs. | ||
| 960 : | The base implementation of this method supplied with the abstract class <tt>BaseInstallHandler | ||
| 961 : | </tt>performs the default click-through processing using the license | ||
| 962 : | text supplied as part of the feature manifest. On return this method indicates | ||
| 963 : | celek | 1.7 | success (installation continues) of failure (installation is aborted).</li> |
| 964 : | celek | 1.9 | <li> install-downloaded - the install handler is called after all the |
| 965 : | required feature files were downloaded (feature, plugins, data) but before | ||
| 966 : | the actual installation is performed. The install handler is expected to | ||
| 967 : | perform verification of the non-plug-in data files (eg. security), or any | ||
| 968 : | other pre-install processing. On return this method indicates success | ||
| 969 : | (installation continues) or failure (installation is aborted).</li> | ||
| 970 : | <li> install-completion - the install handler is called after the feature | ||
| 971 : | information and the plug-ins were installed. It is expected to complete the | ||
| 972 : | installation of any non-plug-in data that was part of the feature. On return | ||
| 973 : | this method indicates success (returns custom install log) or failure (installation | ||
| 974 : | is aborted). On failure, the install handler is expected to perform any | ||
| 975 : | required cleanup.</li> | ||
| 976 : | <li> uninstall-initiated - the install handler is called when a feature | ||
| 977 : | is selected for removal, but before any of the standard uninstall processing | ||
| 978 : | has taken place. It is passed the custom install log created by the install | ||
| 979 : | celek | 1.7 | handler install-completion step.</li> |
| 980 : | celek | 1.9 | <li> uninstall-completion - the install handler is called on completion |
| 981 : | of the standard uninstall steps. It is passed the custom install log created | ||
| 982 : | celek | 1.7 | by the install handler install-completion step.</li> |
| 983 : | celek | 1.9 | |
| 984 : | celek | 1.7 | </ul> |
| 985 : | celek | 1.9 | Note, that as a general practice, install handlers should be provided in |
| 986 : | their own jars (even though they could be just exposed in the feature archive | ||
| 987 : | jar). The jar should be signed, and sealed. | ||
| 988 : | <h3> <a name="Security_Considerations"></a> Security Considerations</h3> | ||
| 989 : | The general approach is to use base Java jar signing for the feature and | ||
| 990 : | plug-in archive .jars. | ||
| 991 : | celek | 1.7 | <p>Features are verified as follows: </p> |
| 992 : | celek | 1.9 | |
| 993 : | celek | 1.7 | <ul> |
| 994 : | celek | 1.9 | <li> download and verify the feature archive (use base Java jar verification)</li> |
| 995 : | <li> for each plug-in archive</li> | ||
| 996 : | |||
| 997 : | <ul> | ||
| 998 : | <li> verify the archive jar content (use base Java jar verification)</li> | ||
| 999 : | <li> verify plug-in id and version from <tt><plugin></tt> entry | ||
| 1000 : | in feature manifest matches downloaded plugin.xml</li> | ||
| 1001 : | |||
| 1002 : | celek | 1.7 | </ul> |
| 1003 : | celek | 1.9 | <li> for each non-plugin file</li> |
| 1004 : | |||
| 1005 : | celek | 1.7 | <ul> |
| 1006 : | celek | 1.9 | <li> call install handler to verify file</li> |
| 1007 : | |||
| 1008 : | celek | 1.7 | </ul> |
| 1009 : | celek | 1.9 | |
| 1010 : | </ul> | ||
| 1011 : | In general, when processing signed jars, the user will be prompted for | ||
| 1012 : | each unrecognized certificate. The response choices will include aborting | ||
| 1013 : | the installation (originator is not trusted), continuing the installation | ||
| 1014 : | (originator is trusted for this installation). | ||
| 1015 : | <h2> <a name="Update_Server"></a> Update Server</h2> | ||
| 1016 : | The default Eclipse update server is any URL-accessible server. The default | ||
| 1017 : | implementation assumes a fixed-layout server. The content of the server | ||
| 1018 : | (in terms of available features and plug-ins) is described in a site map | ||
| 1019 : | file, <i>site.xml</i>. This file can be manually maintained, or can be dynamically | ||
| 1020 : | computed by the server. | ||
| 1021 : | <h3> <a name="Site_Map"></a> Site Map</h3> | ||
| 1022 : | The update server URL can be specified as a full URL to the site map file, | ||
| 1023 : | or a URL of a directory path containing the site map file (similar to index.html | ||
| 1024 : | processing). The site map site.xml format is defined by the following dtd: | ||
| 1025 : | celek | 1.7 | |
| 1026 : | <p><tt><?xml encoding="ISO-8859-1"?></tt> </p> | ||
| 1027 : | celek | 1.9 | |
| 1028 : | <p><tt><!ELEMENT site (description?, feature*, archive*, category-def*)></tt> | ||
| 1029 : | celek | 1.7 | <br> |
| 1030 : | celek | 1.9 | <tt><!ATTLIST site</tt> <br> |
| 1031 : | <tt> type | ||
| 1032 : | CDATA #IMPLIED</tt> <br> | ||
| 1033 : | <tt> url | ||
| 1034 : | CDATA #IMPLIED</tt> <br> | ||
| 1035 : | <tt>></tt> </p> | ||
| 1036 : | |||
| 1037 : | celek | 1.7 | <p><tt><!ELEMENT description (#PCDATA)></tt> <br> |
| 1038 : | celek | 1.9 | <tt><!ATTLIST description</tt> <br> |
| 1039 : | <tt> url | ||
| 1040 : | CDATA #IMPLIED</tt> <br> | ||
| 1041 : | <tt>></tt> </p> | ||
| 1042 : | |||
| 1043 : | celek | 1.7 | <p><tt><!ELEMENT feature (category*)></tt> <br> |
| 1044 : | celek | 1.9 | <tt><!ATTLIST feature</tt> <br> |
| 1045 : | <tt> type | ||
| 1046 : | CDATA #IMPLIED</tt> <br> | ||
| 1047 : | <tt> id | ||
| 1048 : | CDATA #IMPLIED</tt> <br> | ||
| 1049 : | <tt> version CDATA | ||
| 1050 : | celek | 1.7 | #IMPLIED</tt> <br> |
| 1051 : | celek | 1.9 | <tt> url |
| 1052 : | CDATA #REQUIRED<br> | ||
| 1053 : | label CDATA #IMPLIED<br> | ||
| 1054 : | ></tt> </p> | ||
| 1055 : | |||
| 1056 : | celek | 1.7 | <p><tt><!ELEMENT archive EMPTY></tt> <br> |
| 1057 : | celek | 1.9 | <tt><!ATTLIST archive</tt> <br> |
| 1058 : | <tt> path | ||
| 1059 : | CDATA #REQUIRED</tt> <br> | ||
| 1060 : | <tt> url | ||
| 1061 : | CDATA #REQUIRED</tt> <br> | ||
| 1062 : | <tt>></tt> </p> | ||
| 1063 : | |||
| 1064 : | celek | 1.7 | <p><tt><!ELEMENT category EMPTY></tt> <br> |
| 1065 : | celek | 1.9 | <tt><!ATTLIST category</tt> <br> |
| 1066 : | <tt> name | ||
| 1067 : | CDATA #REQUIRED</tt> <br> | ||
| 1068 : | <tt>></tt> </p> | ||
| 1069 : | |||
| 1070 : | celek | 1.7 | <p><tt><!ELEMENT category-def (description?)></tt> <br> |
| 1071 : | celek | 1.9 | <tt><!ATTLIST category-def</tt> <br> |
| 1072 : | <tt> name | ||
| 1073 : | CDATA #REQUIRED</tt> <br> | ||
| 1074 : | <tt> label | ||
| 1075 : | CDATA #REQUIRED</tt> <br> | ||
| 1076 : | <tt>></tt> </p> | ||
| 1077 : | |||
| 1078 : | celek | 1.7 | <p>The element and attribute definitions are as follows: </p> |
| 1079 : | celek | 1.9 | |
| 1080 : | celek | 1.7 | <ul> |
| 1081 : | celek | 1.9 | <li> <site> - defines the site map</li> |
| 1082 : | |||
| 1083 : | celek | 1.7 | <ul> |
| 1084 : | celek | 1.9 | <li> type - optional site type specification. The value refers to a type |
| 1085 : | string registered via the <a href="#Framework">install framework</a> extension | ||
| 1086 : | point. If not specified, the type is assumed to be the default Eclipse site | ||
| 1087 : | type (as specified in this document).</li> | ||
| 1088 : | <li> url - optional URL defining the update site baseline URL (used to | ||
| 1089 : | determine individual <feature> and <archive> location). | ||
| 1090 : | Can be relative or absolute. If relative, is relative to site.xml. If not | ||
| 1091 : | celek | 1.7 | specified, the default is the URL location of the site.xml file.</li> |
| 1092 : | celek | 1.9 | |
| 1093 : | celek | 1.7 | </ul> |
| 1094 : | celek | 1.9 | <li> <description> - brief description as simple text. Intended |
| 1095 : | to be translated.</li> | ||
| 1096 : | |||
| 1097 : | <ul> | ||
| 1098 : | <li> url - optional URL for the full description as HTML. The URL can be | ||
| 1099 : | specified as absolute of relative. If relative, If relative, is relative to | ||
| 1100 : | site.xml.</li> | ||
| 1101 : | <br> | ||
| 1102 : | Note, that for NL handling the URL value should be separated to allow alternate | ||
| 1103 : | URLs to be specified for each national language. | ||
| 1104 : | </ul> | ||
| 1105 : | <li> <feature> - identifies referenced feature archive</li> | ||
| 1106 : | |||
| 1107 : | <ul> | ||
| 1108 : | <li> type - optional feature type specification. The value refers to a | ||
| 1109 : | type string registered via the <a href="#Framework">install framework</a> | ||
| 1110 : | extension point. If not specified, the type is assumed to be the default | ||
| 1111 : | feature type for the site. If the site type is the default Eclipse site type, | ||
| 1112 : | the default feature type is the packaged feature type (as specified in this | ||
| 1113 : | document).</li> | ||
| 1114 : | <li> id - optional feature identifier. The information is used as a performance | ||
| 1115 : | optimization to speed up searches for features. Must match the identifier | ||
| 1116 : | specified in the feature.xml of the referenced archive (the url attribute). | ||
| 1117 : | If specified, the version attribute must also be specified.</li> | ||
| 1118 : | <li> version - optional feature version. The information is used as a | ||
| 1119 : | performance optimization to speed up searches for features. Must match the | ||
| 1120 : | version specified in the feature.xml of the referenced archive (the url attribute). | ||
| 1121 : | If specified, the id attribute must also be specified.</li> | ||
| 1122 : | <li> url - required URL reference to the feature archive. Can be relative | ||
| 1123 : | or absolute. If relative, it is relative to the location of the site.xml file. | ||
| 1124 : | <b>Note</b>: the default site implementation allows features to be accessed | ||
| 1125 : | without being explicitly declared using a <feature> entry. By default, | ||
| 1126 : | an undeclared features reference is interpreted as "features/<id>_<version>.jar"</li> | ||
| 1127 : | <li>label - optional feature label. The value is used for optimization | ||
| 1128 : | when browsing the site from the update manager. Intended to be translated.<br> | ||
| 1129 : | </li> | ||
| 1130 : | |||
| 1131 : | celek | 1.7 | </ul> |
| 1132 : | celek | 1.9 | <li> <archive> - identifies referenced "storage" archive (the actual |
| 1133 : | files referenced via the <tt><plugin></tt> or <tt><data></tt> | ||
| 1134 : | elements in the feature manifest). The site simply manages archives as a | ||
| 1135 : | path-to-URL map. The default Eclipse site implementation does not require | ||
| 1136 : | the <archive> section to be included in the site map (site.xml). Any | ||
| 1137 : | archive reference not explicitly defined as part of an <archive> section | ||
| 1138 : | is assumed to be mapped to a url in the form "<archivePath>" relative | ||
| 1139 : | celek | 1.7 | to the location of the site.xml file.</li> |
| 1140 : | celek | 1.9 | |
| 1141 : | celek | 1.7 | <ul> |
| 1142 : | celek | 1.9 | <li> path - required archive path identifier. This is a string that is |
| 1143 : | determined by the <a href="#Feature_Archive_Mapping_Id_To_Path">feature</a> | ||
| 1144 : | referencing this archive and is not otherwise interpreted by the site (other | ||
| 1145 : | celek | 1.7 | than as a lookup token).</li> |
| 1146 : | celek | 1.9 | <li> url - required URL reference to the archive. Can be relative or absolute. |
| 1147 : | If relative, it is relative to the location of the site.xml file.</li> | ||
| 1148 : | |||
| 1149 : | </ul> | ||
| 1150 : | <li> <category-def> - an optional definition of a category that | ||
| 1151 : | can be used by installation and update support to hierarchicaly organize | ||
| 1152 : | features</li> | ||
| 1153 : | |||
| 1154 : | celek | 1.7 | <ul> |
| 1155 : | celek | 1.9 | <li> name - category name. Is specified as a path of name tokens separated |
| 1156 : | celek | 1.7 | by /</li> |
| 1157 : | celek | 1.9 | <li> label - displayable label. Intended to be translated.</li> |
| 1158 : | |||
| 1159 : | celek | 1.7 | </ul> |
| 1160 : | celek | 1.9 | <li> <category> - actual category specification for a feature entry</li> |
| 1161 : | |||
| 1162 : | celek | 1.7 | <ul> |
| 1163 : | celek | 1.9 | name - category name |
| 1164 : | celek | 1.7 | </ul> |
| 1165 : | celek | 1.9 | |
| 1166 : | celek | 1.7 | </ul> |
| 1167 : | celek | 1.9 | Note, that in general the feature.xml manifest documents should specify |
| 1168 : | UTF-8 encoding. For example | ||
| 1169 : | celek | 1.7 | <p><tt><?xml version="1.0" encoding="UTF-8"?></tt> </p> |
| 1170 : | celek | 1.9 | |
| 1171 : | <p>Translatable text contained in the site.xml can be separated into site<_locale>.properties | ||
| 1172 : | files using Java property bundle conventions. Note that the translated strings | ||
| 1173 : | are used at installation time (ie. do not employ the plug-in fragment runtime | ||
| 1174 : | mechanism). The property bundles are located relative to the site.xml location. | ||
| 1175 : | </p> | ||
| 1176 : | |||
| 1177 : | <h3> <a name="Default_Site_Layout"></a> Default Site Layout</h3> | ||
| 1178 : | <tt><site root>/</tt> <br> | ||
| 1179 : | <tt> site.xml</tt> <br> | ||
| 1180 : | <tt> features/</tt> <br> | ||
| 1181 : | <tt> feature archives | ||
| 1182 : | (eg. org.eclipse.javatools_1.0.1.jar)</tt> <br> | ||
| 1183 : | <tt> <featureId>_<featureVersion>/ | ||
| 1184 : | (optional)</tt> <br> | ||
| 1185 : | <tt> non-plug-in | ||
| 1186 : | celek | 1.7 | files for feature</tt> <br> |
| 1187 : | celek | 1.9 | <tt> plugins/</tt> <br> |
| 1188 : | <tt> plug-in argives | ||
| 1189 : | (eg. org.eclipse.ui_1.0.3.jar)</tt> | ||
| 1190 : | <h3> <a name="Controlling_Access"></a> Controlling Access</h3> | ||
| 1191 : | The default Eclipse site implementation provides support for http access | ||
| 1192 : | with basic user authentication (userid and password). | ||
| 1193 : | <p>Custom access control mechanisms can be added to base Eclipse in one of | ||
| 1194 : | celek | 1.7 | 2 ways: </p> |
| 1195 : | celek | 1.9 | |
| 1196 : | celek | 1.7 | <ul> |
| 1197 : | celek | 1.9 | <li> by supplying server-side logic on the update server (eg. implementing |
| 1198 : | servlets that compute the site.xml map, and control access to individual archives | ||
| 1199 : | based on some user criteria)</li> | ||
| 1200 : | <li> by supplying a custom concrete implementation of the site object | ||
| 1201 : | (installed on the client machine, update server specified <tt><site type=""></tt> | ||
| 1202 : | ). The custom concrete site implementation, together with any server-side | ||
| 1203 : | logic support the required control mechanisms.</li> | ||
| 1204 : | |||
| 1205 : | vlad | 1.1 | </ul> |
| 1206 : | celek | 1.9 | Eclipse provides an example demonstrating an implementation of an access |
| 1207 : | mechanism based on feature key files. | ||
| 1208 : | <h2> <a name="Eclipse_Install"></a> Eclipse Install</h2> | ||
| 1209 : | |||
| 1210 : | <h3> <a name="Default_Install_Layout"></a> Default Install Layout</h3> | ||
| 1211 : | <tt><install root>/</tt> <br> | ||
| 1212 : | <tt> install/</tt> <br> | ||
| 1213 : | <tt> features/</tt> <br> | ||
| 1214 : | <tt> <featureId>_<version>/</tt> | ||
| 1215 : | <br> | ||
| 1216 : | <tt> | ||
| 1217 : | feature.xml</tt> <br> | ||
| 1218 : | <tt> | ||
| 1219 : | other feature files</tt> <br> | ||
| 1220 : | <tt> | ||
| 1221 : | META-INF/</tt> <br> | ||
| 1222 : | <tt> | ||
| 1223 : | META-INF-ECLIPSE/</tt> | ||
| 1224 : | celek | 1.7 | <p><tt> plugins/</tt> <br> |
| 1225 : | celek | 1.9 | <tt> <pluginORfragmentId>_<version>/</tt> |
| 1226 : | celek | 1.7 | <br> |
| 1227 : | celek | 1.9 | <tt> plugin.xml |
| 1228 : | celek | 1.7 | or fragment.xml</tt> <br> |
| 1229 : | celek | 1.9 | <tt> other |
| 1230 : | celek | 1.7 | plugin or fragment files</tt> <br> |
| 1231 : | celek | 1.9 | <tt> META_INF/</tt> |
| 1232 : | celek | 1.7 | </p> |
| 1233 : | celek | 1.9 | |
| 1234 : | <p><b>Implementation Note:</b> we will go back to the original design of | ||
| 1235 : | not splitting out fragments (ie. plugin and fragments go into the same install | ||
| 1236 : | celek | 1.7 | location) </p> |
| 1237 : | celek | 1.9 | |
| 1238 : | <h3> <a name="Unmanaged_Plugins"></a> "Unmanaged" Plug-Ins</h3> | ||
| 1239 : | Eclipse supports a concept of "unmanaged" plug-ins. These are plug-ins | ||
| 1240 : | that were directly installed into the Eclipse file tree without being part | ||
| 1241 : | of a feature (eg. developer unzipping plug-in archive directly into the Eclipse | ||
| 1242 : | file tree). | ||
| 1243 : | <p>Eclipse runtime recognizes these plugins during startup and loads the | ||
| 1244 : | plug-in information into the runtime registry following the standard plug-in | ||
| 1245 : | binding rules. The update support also recognizes the presence of this new | ||
| 1246 : | plug-in, but since this plug-in is not part of any feature it cannot be updated | ||
| 1247 : | using the update support (hence "unmanaged"). Unmanaged plug-in that become | ||
| 1248 : | referenced by a feature as a result of some future installation or update | ||
| 1249 : | action become "managed" (can be updated as part of the feature). </p> | ||
| 1250 : | |||
| 1251 : | <p>Unmanaged plug-ins are not displayed as part of the installation and update | ||
| 1252 : | celek | 1.7 | UI. </p> |
| 1253 : | celek | 1.9 | |
| 1254 : | <h3> <a name="Using_Native_Platform_Installers"></a> Using Native Platform | ||
| 1255 : | Installers</h3> | ||
| 1256 : | The Eclipse installation contains plugins that can be shared across multiple | ||
| 1257 : | features. When installing and uninstalling features using the Eclipse installation | ||
| 1258 : | and update support, these relationship are correctly maintained. Only one | ||
| 1259 : | copy of any version of a plug-in is used. | ||
| 1260 : | <p>However, when using native platform installers, performing native uninstall | ||
| 1261 : | creates problems because plug-ins would be removed without regard to any | ||
| 1262 : | sharing relationships. As a result, Eclipse <b>does not allow</b> plug-ins | ||
| 1263 : | to be installed using native installers into the shared installation tree. | ||
| 1264 : | Instead, native installers must establish their own installation root directory. | ||
| 1265 : | The subdirectory structure is the same as defined for base Eclipse. The private | ||
| 1266 : | root directory is logically linked into the shared Eclipse installation via | ||
| 1267 : | a link file installed by the native installer. The file path for the link | ||
| 1268 : | file is <tt><configRoot>/links/</tt>. The <tt><configRoot> </tt> | ||
| 1269 : | location is computed by Eclipse relative to the launch <a | ||
| 1270 : | href="#Multiple%20Launch%20Points"> configuration file</a> . By default, | ||
| 1271 : | this is the <tt>install/</tt> directory in the shared Eclipse installation | ||
| 1272 : | tree. </p> | ||
| 1273 : | |||
| 1274 : | <p>The name of the link file is not specified by Eclipse. The name is determined | ||
| 1275 : | by the native installer. To minimize the potential for naming collisions, | ||
| 1276 : | it is recommended that the file name contain the identifier and version | ||
| 1277 : | of the feature being installed by the native installer. For example, <tt><featureId>_<featureVersion>.properties</tt> | ||
| 1278 : | . The file content is in the form of a Java properties file, with the following | ||
| 1279 : | properties defined: </p> | ||
| 1280 : | |||
| 1281 : | celek | 1.7 | <p><tt>path=[r|rw] install-path[,[r|rw] install-path]*</tt> </p> |
| 1282 : | celek | 1.9 | |
| 1283 : | <p>The property <tt>path</tt> is a comma-separated list of optionally annotated | ||
| 1284 : | install paths. The property value <tt>install-path</tt> is a full file path | ||
| 1285 : | to the installation directory root, specified in local OS format. The optional | ||
| 1286 : | annotation <tt>r</tt> or <tt>rw</tt> indicates whether Eclipse update support | ||
| 1287 : | should allow the specified location to be used for updates. Default is to | ||
| 1288 : | celek | 1.7 | allow updates (w). </p> |
| 1289 : | celek | 1.9 | |
| 1290 : | <p>Eclipse does not manage the linked directories in any way. It simply detects | ||
| 1291 : | their existence by the presence of the link files, and includes the linked | ||
| 1292 : | plug-ins during the platform startup. The native installer is responsible | ||
| 1293 : | for uninstalling the link when the corresponding directory is removed. Eclipse | ||
| 1294 : | celek | 1.7 | runtime ignores any links that cannot be resolved. <br> |
| 1295 : | celek | 1.9 | </p> |
| 1296 : | <br> | ||
| 1297 : | vlad | 1.1 | </body> |
| 1298 : | </html> |
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |