SetUpEclipseForPlugin - Revision history

JenniferVendetti: corrected the url for downloading the ant template. it had moved from the bin to the etc directory in subversion.

2011-03-31T21:40:23Z

corrected the url for downloading the ant template. it had moved from the bin to the etc directory in subversion.

TaniaTudorache at 00:19, March 21, 2009

2009-03-21T00:19:42Z

TaniaTudorache at 22:35, March 20, 2009

2009-03-20T22:35:36Z

TaniaTudorache at 22:34, March 20, 2009

2009-03-20T22:34:30Z

TaniaTudorache at 22:34, March 20, 2009

2009-03-20T22:34:15Z

Tredmond: /* Prerequisites */

2009-03-20T19:09:24Z

‎Prerequisites

Tredmond: /* Prerequisites */

2009-03-20T19:08:44Z

‎Prerequisites

Tredmond: /* Prerequisites */

2009-03-20T19:08:27Z

‎Prerequisites

TaniaTudorache at 18:56, March 20, 2009

2009-03-20T18:56:35Z

TaniaTudorache at 18:55, March 20, 2009

2009-03-20T18:55:35Z

← Older revision		Revision as of 21:40, March 31, 2011
Line 264:		Line 264:
	=== Using ant for compiling and running ===		=== Using ant for compiling and running ===

−	If you are experienced with [http://ant.apache.org/ ant], you can customize an ant template that we provide for compiling, installing and running the plug-in. The ant template is available [http://smi-protege.stanford.edu/svn/protege-core/trunk/~~bin~~/template-plugin-build.xml~~?rev=13453&view=log~~ here] (Click ''view'' for the latest revision). You will need to set a ''PROTEGE_HOME'' environment variable that points to the Protege installation directory. The rest of the template customization only consists in adapting the name and path of the plug-in, and possibly the dependencies. We have a page describing how to use ant targets for Protege plug-ins in Eclipse [[ConfiguringAntBuildFiles\|here]].	+	If you are experienced with [http://ant.apache.org/ ant], you can customize an ant template that we provide for compiling, installing and running the plug-in. The ant template is available [http://smi-protege.stanford.edu/svn/protege-core/trunk/etc/template-plugin-build.xml here] (Click ''view'' for the latest revision). You will need to set a ''PROTEGE_HOME'' environment variable that points to the Protege installation directory. The rest of the template customization only consists in adapting the name and path of the plug-in, and possibly the dependencies. We have a page describing how to use ant targets for Protege plug-ins in Eclipse [[ConfiguringAntBuildFiles\|here]].

← Older revision		Revision as of 00:19, March 21, 2009
Line 264:		Line 264:
	=== Using ant for compiling and running ===		=== Using ant for compiling and running ===

−	If you are experienced with [http://ant.apache.org/ ant], you can customize an ant template that we provide for compiling, installing and running the plug-in. The ant template is available [http://smi-protege.stanford.edu/svn/protege-core/trunk/bin/template-plugin-build.xml?rev=13453&view=log here] (Click ''view'' for the latest revision). You will need to set a ''PROTEGE_HOME'' environment variable that points to the Protege installation directory. The rest of the template customization only consists in adapting the name and path of the plug-in, and possibly the dependencies.	+	If you are experienced with [http://ant.apache.org/ ant], you can customize an ant template that we provide for compiling, installing and running the plug-in. The ant template is available [http://smi-protege.stanford.edu/svn/protege-core/trunk/bin/template-plugin-build.xml?rev=13453&view=log here] (Click ''view'' for the latest revision). You will need to set a ''PROTEGE_HOME'' environment variable that points to the Protege installation directory. The rest of the template customization only consists in adapting the name and path of the plug-in, and possibly the dependencies. We have a page describing how to use ant targets for Protege plug-ins in Eclipse [[ConfiguringAntBuildFiles\|here]].

← Older revision		Revision as of 22:35, March 20, 2009
Line 276:		Line 276:
	* The exported jar does not have the right manifest in it.		* The exported jar does not have the right manifest in it.

−	For all cases, please recheck that the ''META-INF/MANIFEST.MF'' file is at the right location and contains the right java class in it (it should point to the class that extends the plugin class!). Read more about creating the manifest file [PluginManifestsAndJars\|here]. Look also in the console if you have any exceptions. If after rechecking the manifest file, you are still lost, please send an email to the protege mailing list (see ''Where to report problems'' section) and attach any exception you get in the console.	+	For all cases, please recheck that the ''META-INF/MANIFEST.MF'' file is at the right location and contains the right java class in it (it should point to the class that extends the plugin class!). Read more about creating the manifest file [[PluginManifestsAndJars\|here]]. Look also in the console if you have any exceptions. If after rechecking the manifest file, you are still lost, please send an email to the protege mailing list (see ''Where to report problems'' section) and attach any exception you get in the console.

@@ Line 13: / Line 13: @@
 #Download and install Eclipse from [http://www.eclipse.org/downloads/ here].
 #Download and install latest version of Protege 3.x from [http://protege.stanford.edu/download/download.html here].  Let's say you have installed Protege in: <code>/work/protege/Protege_3.4.</code>
 == Setting up Eclipse ==

@@ Line 12: / Line 12: @@
 #Download and install Eclipse from [http://www.eclipse.org/downloads/ here].
-#Download and install latest version of Protege 3.x from [http://protege.stanford.edu/download/download.html here]. Let's say you have installed Protege in: <pre>/work/protege/Protege_3.4.</pre>
+#Download and install latest version of Protege 3.x from [http://protege.stanford.edu/download/download.html here].  Let's say you have installed Protege in: <code>/work/protege/Protege_3.4.</code>
 == Setting up Eclipse ==
@@ Line 256: / Line 256: @@
 To try out the plug-in in Protege, you have to create a subfolder of ''plugins'' in your Protege installation directory. For example, we could create a subfolder called: ''plugins/mytab''. (Usually people use the Java package name as the sufolder name, but it is not required). Then copy the generated jar in this subfolder and start Protege. We have detailed [[PluginManifestsAndJars|documentation]] about how to create a jar for your plug-in for the different plug-in types.

← Older revision		Revision as of 18:56, March 20, 2009
Line 256:		Line 256:


−	To try out the plug-in in Protege, you have to create a subfolder of ''plugins'' in your Protege installation directory. For example, we could create a subfolder called: ''~~pulgins~~/mytab''. (Usually people use the Java package name as the sufolder name, but it is not required). Then copy the generated jar in this subfolder and start Protege. We have detailed [[PluginManifestsAndJars\|documentation]] about how to create a jar for your plug-in for the different plug-in types.	+	To try out the plug-in in Protege, you have to create a subfolder of ''plugins'' in your Protege installation directory. For example, we could create a subfolder called: ''plugins/mytab''. (Usually people use the Java package name as the sufolder name, but it is not required). Then copy the generated jar in this subfolder and start Protege. We have detailed [[PluginManifestsAndJars\|documentation]] about how to create a jar for your plug-in for the different plug-in types.

← Older revision		Revision as of 18:55, March 20, 2009
Line 237:		Line 237:
	Below are the steps for creating a jar.		Below are the steps for creating a jar.

		+	Right click on ''src -> Export -> open Java -> JAR file -> click Next''. In the next window, select ''src'', open the node and '''unselect META-INF''' (important!). Then add a path where the jar should be exported to. See below:


		+	[[Image:Eclipse_plugin_export_jar.png]]

		+
		+	You could set as the path to which you export the plugin folder where the plug-in should actually be.
		+
		+	Click ''Next''. In the next window, you can save the description of this jar in the workspace, in case you will want to generate later the jar again, by just one click (optional). Then, click ''Next'.
		+
		+	In the next window, you have to specify what manifest file should be used for the jar. Select ''Use manifest file from workspace'' and browse to the ''MANIFEST.MF'' in the workspace (In this example, ''/HelloWorldTab/src/META-INF/MANIFEST.MF''). See below:
		+
		+
		+	[[Image:Eclipse_plugin_jar_export_manifest.png]]
		+
		+
		+	Click ''Finish''. The jar will be generated in the location you have set up in the first export step.
		+
		+
		+	To try out the plug-in in Protege, you have to create a subfolder of ''plugins'' in your Protege installation directory. For example, we could create a subfolder called: ''pulgins/mytab''. (Usually people use the Java package name as the sufolder name, but it is not required). Then copy the generated jar in this subfolder and start Protege. We have detailed [[PluginManifestsAndJars\|documentation]] about how to create a jar for your plug-in for the different plug-in types.