CompileProtege4InEclipseFromSvn - Revision history

JenniferVendetti at 18:36, April 24, 2013

2013-04-24T18:36:35Z

TaniaTudorache: changed http -> https for protege svn repo

2013-03-19T21:47:15Z

changed http -> https for protege svn repo

Swartik: Fixed some lower-case button names.

2011-04-20T13:37:48Z

Fixed some lower-case button names.

Swartik: Removed an extra "and".

2011-04-20T13:20:18Z

Removed an extra "and".

Tredmond: /* Configuring Eclipse */

2011-04-19T21:29:58Z

‎Configuring Eclipse

Tredmond: /* Configuring Eclipse */

2011-04-19T21:26:11Z

‎Configuring Eclipse

Tredmond: /* Configuring Eclipse */

2011-04-19T21:25:24Z

‎Configuring Eclipse

Tredmond: /* Configuring Eclipse */

2011-04-19T21:24:44Z

‎Configuring Eclipse

Tredmond: /* Configuring Eclipse */

2011-04-19T21:20:49Z

‎Configuring Eclipse

Tredmond at 21:12, April 19, 2011

2011-04-19T21:12:57Z

← Older revision		Revision as of 18:36, April 24, 2013
Line 1:		Line 1:
−	= Instructions for Compiling and Running Protege 4.1 in Eclipse using the sources from SVN =	+	= Instructions for Compiling and Running Protege 4.1+ in Eclipse using the sources from SVN =

	These instructions will help you set up the Eclipse environment for Protege 4.1. In the first part, we will check out from SVN a Eclipse workspace already configured for Protege 4.1 and its plugins, then in the second part, we will show how to add your own plugin in Eclipse.		These instructions will help you set up the Eclipse environment for Protege 4.1. In the first part, we will check out from SVN a Eclipse workspace already configured for Protege 4.1 and its plugins, then in the second part, we will show how to add your own plugin in Eclipse.

@@ Line 19: / Line 19: @@
 '''Step 1: Checking out the workspace''' Use subversion to checkout the following workspace:
 <pre>
-     http://smi-protege.stanford.edu/repos/protege/protege4/ide/eclipse/protege4.1/trunk
+     https://smi-protege.stanford.edu/repos/protege/protege4/ide/eclipse/protege4.1/trunk
 </pre>
 If you are using command line tools you can do this with the svn command
 <pre>
-     svn checkout http://smi-protege.stanford.edu/repos/protege/protege4/ide/eclipse/protege4.1/trunk protege4.1
+     svn checkout https://smi-protege.stanford.edu/repos/protege/protege4/ide/eclipse/protege4.1/trunk protege4.1
 </pre>
 This creates an eclipse workspace but some of the metadata is still missing.
@@ Line 83: / Line 83: @@
 '''Easy way'''.  If you are able to run protege the easy way (4a) then your plugin will be included. Hotspot replace works (some of the time as always).
-'''Harder way'''. If you run protege the harder way (4b) then you will need to install your plugin into the protege distribution that we have created.  To do this you will need an ant build file.  We have provided a [http://smi-protege.stanford.edu/repos/protege/protege4/protege-base/trunk/etc/template-plugin-build.xml template build file] that can easily be filled in.  We will now describe how this script is added as an eclipse build script.  We will turn the fact that I forgot to install the dlquery build script in eclipse into an advantage by showing how this is added here.
+'''Harder way'''. If you run protege the harder way (4b) then you will need to install your plugin into the protege distribution that we have created.  To do this you will need an ant build file.  We have provided a [https://smi-protege.stanford.edu/repos/protege/protege4/protege-base/trunk/etc/template-plugin-build.xml template build file] that can easily be filled in.  We will now describe how this script is added as an eclipse build script.  We will turn the fact that I forgot to install the dlquery build script in eclipse into an advantage by showing how this is added here.
 To create this new eclipse build script, click on the down arrow to the right of the suitcase runnable and click on "External Tool Configurations".  Select "Ant Build" and click the "New Launch Configuration" just above the selected "Ant Build" option.  In the resulting window, set the name to "Build.DlQuery" and browse the workspace for the DLQuery build.xml file.  The result should look like this:

@@ Line 36: / Line 36: @@
 </pre>
-'''Step 3: Load the Workspace'''  Start eclipse and choose the newly created directory as the workspace.  Since this is a new workspace, eclipse comes up with a welcome screen which you can dismiss.  We now import the projects.  Go to the file menu and click "File->Import".  You should get a window as shown below and can open the "General" tree to see and select the "Existing Projects into workspace".
+'''Step 3: Load the Workspace'''  Start eclipse and choose the newly created directory as the workspace.  Since this is a new workspace, eclipse comes up with a welcome screen which you can dismiss.  We now import the projects.  Go to the file menu and click "File->Import".  You should get a window as shown below and can open the "General" tree to see and select the "Existing Projects into Workspace".
 [[File:EasyP4EclipseImportProjects.png|frame|none|]]
-Once "Existing Projects into Workspace" has been selected click next.  This should give you the window shown below.
+Once "Existing Projects into Workspace" has been selected click Next.  This should give you the window shown below.
 [[File:EasyP4EclipseImportProjects02.png|frame|none]]
-Click the browse button to select the workspace directory.
+Click the Browse button to select the workspace directory.
 [[File:EasyP4EclipseImportProjects03.png|frame|none]]
@@ Line 52: / Line 52: @@
 [[File:EasyP4EclipseImportProjects04.png|frame|none]]
-Click finish and the files should be imported.
+Click Finish and the files should be imported.
 [[File:EasyP4EclipseProjectsImported.png|frame|none]]

@@ Line 44: / Line 44: @@
 [[File:EasyP4EclipseImportProjects02.png|frame|none]]
-Click the browse button to and select the workspace directory.
+Click the browse button to select the workspace directory.
 [[File:EasyP4EclipseImportProjects03.png|frame|none]]

@@ Line 68: / Line 68: @@
 # Build.Common
 # Build.Core
 # Build.Owlapi.Lib
 # Build.Owl.Editor

← Older revision		Revision as of 21:26, April 19, 2011
Line 55:		Line 55:

	[[File:EasyP4EclipseProjectsImported.png\|frame\|none]]		[[File:EasyP4EclipseProjectsImported.png\|frame\|none]]
		+
		+	Now all the projects have been loaded into eclipse.

	'''Step 4a: Run Protege (The easy and better way)''' This step can be a bit problematic on the mac but works for linux and windows machines. Just recently this method seems to have started working with Snow Leopard and the latest eclipse (Helios).		'''Step 4a: Run Protege (The easy and better way)''' This step can be a bit problematic on the mac but works for linux and windows machines. Just recently this method seems to have started working with Snow Leopard and the latest eclipse (Helios).

← Older revision		Revision as of 21:20, April 19, 2011
Line 39:		Line 39:

	[[File:EasyP4EclipseImportProjects.png\|frame\|none\|]]		[[File:EasyP4EclipseImportProjects.png\|frame\|none\|]]
		+
		+	Once "Existing Projects into Workspace" has been selected click next. This should give you the window shown below.
		+
		+	[[File:EasyP4EclipseImportProjects02.png\|frame\|none]]
		+
		+	Click the browse button to and select the workspace directory.
		+
		+	File:EasyP4EclipseImportProjects03.png
		+
		+	Once you have selected the workspace you should see the window below that includes the projects that you want to import.
		+