blob: a68f635355e1e3fb5e872652cd36d56393fd0fb7 [file] [log] [blame]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>The Eclipse 3.0 Runtime</title>
<link rel="stylesheet" title="default" href="http://eclipse.org/default_style.css" type="text/css">
<style>
th,td { vertical-align:top; text-align=left}
.issue { font-style:oblique; width:200px;}
.box { background-color:#E0E0FF}
</style>
</head>
<body>
<table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
<tr>
<td ALIGN=left width="60%">
<p><font class=indextop> eclipse</font><br>
<font class=indexsub> 3.0 runtime</font> </p>
</td>
<td WIDTH="40%">&nbsp; </td>
</tr>
</table>
<blockquote>
<p><b>Summary</b><br>
This document introduces the Eclipse 3.0 runtime based on OSGi and details
the concepts of plug-ins, extensions as well as various OSGi topics and how
the runtime starts and manages plug-ins and how the runtime itself is managed.<br>
Last Modified: 1800 December 11, 2003</p>
</blockquote>
<table border=0 cellspacing=0 cellpadding=2 width="100%" >
<tr>
<td align=LEFT valign=TOP colspan="2" bgcolor="#0080C0"><b><font color="#FFFFFF">
Overview</font></b></td>
</tr>
</table>
<p> The Eclipse 3.0 runtime consists of two main pieces; the execution framework
and the extensions registry. The execution engine manages componentsThe execution
engine is an implementation of the <a href="http://www.osgi.org">OSGi</a> framework
specification. </p>
<p>The extensions registry is a mechanism for describing relationships between
</p>
<p>Note: Throughout this document we use the terms <i>plug-in</i> and <i>bundle</i>
interchangeably unless we are refering to the actual <tt>Plugin</tt> or <tt>Bundle</tt>
classes. Just as in Eclipse 2.1, some plug-ins/bundles may specify extensions
or extension-points and some may not.</p>
<p>&nbsp;</p>
</body>
</html>