From Protege Wiki
Instructions for Compiling and Running Protege 4.1 in IntelliJ 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.
To follow these directions you will need the following tools:
- IntelliJ 9 (naturally) with
- The OSGI (Osmorc) plugin enabled.
- The Subversion version control system enabled.
- A tool for extracting a zip file into a directory.
- A tool for checking out a repository from subversion (e.g. tortoise or the svn command line client).
These directions are based on a preconfigured workspace which you can use for the build.
Step 1: Checking out the workspace Use subversion to checkout the following workspace:
If you are using command line tools you can do this with the svn command
svn checkout http://smi-protege.stanford.edu/repos/protege/protege4/ide/idea/protege4.1
This creates all the files you need to compile, but without the IntelliJ configuration. Note that when using Tortoise svn, you need to do a full recursive checkout. It may appear that there is only one file in the repository but the svn checkout needs to also checkout the external references.
Step 2: Install the IntellJ configuration Inside the directory that you just checked out is a file called idea.zip. Extract this file into the created directory. Now the directory location is all ready for IntelliJ. Note that on the mac, double-clicking the metadata.zip file does not do the right thing; it does not simple extract the files into the current directory. So on the mac the command line unzip is probably recommended:
Step 3: Load the Project Start idea and click on File -> Open Project and choose the newly created directory.
Step 4: Run Protege Click on the run button or hit shift-F10. This should start Protege.
Note that when starting Protege in this way, the mechanism by which the plugins are found is different than the mechanism that Protege uses when it is distributed. When Protege is distributed, it scans the plugin directory and find the plugins there. When Protege is started in this manner, OSGI is loading the plugins for Protege. In fact, Protege will report "No Plugins Found" because it does not find a plugin directory and thus did not find any plugins to load. But if you enter "status" in the console you will see a detailed description of the state of the run including a description of what plugins have been found.
Protege will attempt to upgrade the Owlviz Plug-In. Close the Automatic Update window and ignore this for now.