TaniaTudorache at 23:55, May 29, 2008

2008-05-29T23:55:29Z

TaniaTudorache at 23:55, May 29, 2008

2008-05-29T23:55:12Z

JenniferVendetti: New page: Tips for packaging your plug-in for distribution In Protege versions 2.1 and higher, each plug-in resides in a separate, uniquely n...

2008-02-24T00:56:22Z

New page: <span style="font-weight:bold; font-size:18px;">Tips for packaging your plug-in for distribution</span> In Protege versions 2.1 and higher, each plug-in resides in a separate, uniquely n...

New page

<span style="font-weight:bold; font-size:18px;">Tips for packaging your plug-in for distribution</span>

In Protege versions 2.1 and higher, each plug-in resides in a separate, uniquely named subdirectory of the <code>plugins</code> directory and is loaded by a separate class loader. Prior to version 2.1, all plug-ins were placed at the same level in the <code>plugins</code> directory, which caused problems when plug-ins required incompatible versions of the same library. Thanks go to Ian Dickinson at HP Labs for originally suggesting the implementation technique for handling the "plug-in conflict" problem.

Below is a screen shot of the typical Protege directory structure:

[[Image:Protege_Plugins_Directory.jpg|none]]

If you package your plug-in for distribution as a ZIP file, you need to have a "path" inside of the ZIP that corresponds to the directory name that you want your plug-in to use. Then, when a user unzips to the <code>plugins</code> directory, your JAR and other files will end up in the correct subdirectory.

It is essential that each plug-in be placed in a directory with a unique name. In order to ensure unique names, we suggest the scheme illustrated above of using a directory with an "inverted URL" that you "own" and a name for your plug-in. Typically, such a URL has been used as the package name for your plug-in.

Below is a screen shot of a Protege plug-in that has been packaged for distribution in ZIP format. Note the "Path" in the ZIP file, which allows a user to unzip the file to the correct subdirectory of the <code>plugins</code> directory.

[[Image:Plugin_ZIP_Distribution.jpg|none]]

← Older revision		Revision as of 23:55, May 29, 2008
Line 24:		Line 24:


−	If ~~you~~ plugin '''depends on another plugin''' (e.g. your plugin depends on the protege-owl plugin), please read the [http://protegewiki.stanford.edu/index.php/PluginDependencies Plugin Dependencies page].	+	If your plugin '''depends on another plugin''' (e.g. your plugin depends on the protege-owl plugin), please read the [http://protegewiki.stanford.edu/index.php/PluginDependencies Plugin Dependencies page].

← Older revision		Revision as of 23:55, May 29, 2008
Line 21:		Line 21:

	[[Image:Plugin_ZIP_Distribution.jpg\|none]]		[[Image:Plugin_ZIP_Distribution.jpg\|none]]
		+
		+
		+
		+	If you plugin '''depends on another plugin''' (e.g. your plugin depends on the protege-owl plugin), please read the [http://protegewiki.stanford.edu/index.php/PluginDependencies Plugin Dependencies page].

PluginDistribution - Revision history

TaniaTudorache at 23:55, May 29, 2008

TaniaTudorache at 23:55, May 29, 2008

JenniferVendetti: New page: Tips for packaging your plug-in for distribution In Protege versions 2.1 and higher, each plug-in resides in a separate, uniquely n...