blob: bf957a1f03b2d1a8ce4862b8f55b740667a2f689 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><HTML>
<HEAD>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Runtime page</title>
</head>
<BODY BGCOLOR="#ffffff">
<h2>Runtime page</h2>
<p align="left">The <strong>Runtime</strong> page shows all the packages that
your plug-in makes visible to other plug-ins. </p>
<p align="left">Press the <strong>Add...</strong> button in the <strong>Exported
Packages</strong> section to add the <em>com.example.xyz</em> and <em>com.example.xyz.actions</em>
packages to the list.</p>
<p align="center"> <img src="images/plugin-runtime.png" alt="Runtime editor page" border="0" ></p>
<p>The <strong>Package Visibility</strong> section allows you to control on a
per-package basis the visibility of your plug-in code to downstream plug-ins.
Refer to the <a href="restrictions.htm">Access Restrictions</a> document for
full details.</p>
<p>The <strong>Classpath</strong> section is the place to declare the names of
the libraries that constitute the plug-in classpath. Since JAR'd plug-ins are
the recommended format for 3.1, it is recommended to leave this section blank.</p>
</body>
</html>