blob: 55eb6969404f56083deafeb615a36d48c7f57954 [file] [log] [blame]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>The Equinox Project - Dynamic plugins</title>
<link rel="stylesheet" href="http://eclipse.org/default_style.css" type="text/css">
</head>
<body>
<center>
<font class=indextop>equinox</font><br>
<font class=indexsub> eclipse runtime exploration</font><p></p>
<a href="../index.html">[home]</a>
<a href="../documents.html">[documents]</a>
<a href="../downloads.html">[downloads]</a>
<a href="../areas.html">[work areas]</a>
<a href="../resources.html">[resources]</a>
<a href="../faq.html">[faq]</a>
</center>
<br>
<table BORDER=0 CELLSPACING=0 CELLPADDING=2 WIDTH="100%" >
<tr>
<td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font color="#FFFFFF">
Dynamic Plug-ins</font></b></td>
</tr>
</table>
<p> The goal of the DynamicPlugins work is to make writing, maintaining and using
dynamic plug-ins both easier and more failsafe. An overview
of the plug-in states is given
<a href="state_description.html">here</a>.The main issues involved are: </p>
<ul>
<li><a href="deactivatingPlugins.html">Deactivating plugins</a> whose main problem is
<ul>
<li>managing <a href="classloadersAndInstances.html">classloaders and loaded classes</a> </li>
</ul>
</li>
<li><a href="beingGood.html">How to be a good dynamic plugin</a></li>
<li>Mechanisms to support being a good dynamic plug-in</li>
</ul>
<p><img src="http://www.eclipse.org/images/new.gif" width="31" height="14"> <a href="glossary.html">Glossary</a>
of terms used in the dynamic plugin area is available.</p>
<table BORDER=0 CELLSPACING=0 CELLPADDING=2 WIDTH="100%" >
<tr>
<td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font color="#FFFFFF">
Contributors</font></b></td>
</tr>
</table>
<ul>
</ul>
</body>
</html>