| 11 |
<body> |
<body> |
| 12 |
|
|
| 13 |
<h1> Eclipse-based Products and Extensions</h1> |
<h1> Eclipse-based Products and Extensions</h1> |
| 14 |
<p>Last modified 22:30 Sunday April 28, 2002</p> |
<p>Last modified 15:00 Thursday May 9, 2002</p> |
| 15 |
<p>Eclipse technology is the foundation of, and provides building blocks for, |
<p>Eclipse technology is the foundation of, and provides building blocks for, |
| 16 |
products aimed at the software development tools market. Commercial software |
products aimed at the software development tools market. Commercial software |
| 17 |
vendors are expected to build, brand, and package products using the Eclipse |
vendors are expected to build, brand, and package products using the Eclipse |
| 22 |
box, label, or price tag. The closest that the Eclipse project gets to a |
box, label, or price tag. The closest that the Eclipse project gets to a |
| 23 |
packaged form is the Eclipse SDK, which can be downloaded from <a href="http://www.eclipse.org">eclipse.org</a>, |
packaged form is the Eclipse SDK, which can be downloaded from <a href="http://www.eclipse.org">eclipse.org</a>, |
| 24 |
installed, and used as a full-service Java IDE which also happens to include |
installed, and used as a full-service Java IDE which also happens to include |
| 25 |
special support for developing Eclipse plug-ins.</p> |
special support for developing Eclipse plug-ins (PDE).</p> |
| 26 |
<p>This note describes how the Eclipse platform is designed to be turned into products. |
<p>This note describes how the Eclipse platform is designed to be turned into products. |
| 27 |
The license governing the Eclipse platform gives a software vendor almost |
The license governing the Eclipse platform gives a software vendor almost |
| 28 |
complete freedom over how to built a product. So anyone building a product is |
complete freedom over how to built a product. So anyone building a product is |
| 70 |
</code>Eclipse Java launcher<code><br> |
</code>Eclipse Java launcher<code><br> |
| 71 |
install.ini |
install.ini |
| 72 |
</code>install info<code><br> |
</code>install info<code><br> |
| 73 |
platform.cfg |
.config/ |
| 74 |
</code>install info (computed at install time)<code><br> |
</code>install info (computed at install time with -initialize option)<code><br> |
| 75 |
|
platform.cfg |
| 76 |
|
</code>default platform configuration<code><br> |
| 77 |
jre/ |
jre/ |
| 78 |
</code>Java runtime environment (JRE)<code><br> |
</code>Java runtime environment (JRE)<code><br> |
| 79 |
|
|
| 147 |
perspective, and customization of the default settings of plug-in preferences. |
perspective, and customization of the default settings of plug-in preferences. |
| 148 |
Strictly speaking, a product could have more than one primary feature; the |
Strictly speaking, a product could have more than one primary feature; the |
| 149 |
selection of which primary feature gets control is done via the <code>-feature</code> |
selection of which primary feature gets control is done via the <code>-feature</code> |
| 150 |
command line option to <code>eclipse.exe</code>. A typical product has |
command line option to <code>eclipse.exe</code>. The typical product has |
| 151 |
just one eligible primary feature.</p> |
just one eligible primary feature.</p> |
| 152 |
<p>Summary of characteristics of products:</p> |
<p>Summary of characteristics of products:</p> |
| 153 |
<ul> |
<ul> |
| 174 |
<h2>Extensions to Eclipse-based products</h2> |
<h2>Extensions to Eclipse-based products</h2> |
| 175 |
<p>An <b>extension</b> is bundle of Eclipse-based features designed to be |
<p>An <b>extension</b> is bundle of Eclipse-based features designed to be |
| 176 |
installed separately and used with any Eclipse-based product. In contrast to a product, |
installed separately and used with any Eclipse-based product. In contrast to a product, |
| 177 |
an extension includes neither |
an extension includes neither eligible primary features, nor a copy of the Eclipse platform, nor its own JRE.</p> |
|
primary features, nor a copy of the Eclipse platform, n or its own JRE.</p> |
|
| 178 |
<p>The same installed base of files for an extension can be used from several |
<p>The same installed base of files for an extension can be used from several |
| 179 |
Eclipse-based products. This means an extension only needs to be updated in one |
Eclipse-based products. This means an extension only needs to be updated in one |
| 180 |
place, while having the effects felt in all products linked to that extension.</p> |
place, while having the updated features available to all products linked to that extension.</p> |
| 181 |
<p>To keep things concrete, the top level structure of an installed |
<p>To keep things concrete, the top level structure of an installed |
| 182 |
Eclipse-based extension looks like this: </p> |
Eclipse-based extension looks like this: </p> |
| 183 |
<p><code><<i>extension install</i>>/<br> |
<p><code><<i>extension install</i>>/<br> |
Parent Directory
| 
Revision Log
| 
Patch