Difference between revisions of "Software Development Kit"
| Line 6: | Line 6: | ||
The high-level steps for creating, testing and releasing a plugin are as follows: | The high-level steps for creating, testing and releasing a plugin are as follows: | ||
| + | |||
| + | # Edit the provided Apache Ant build script to specify the name of your plugin. | ||
| + | # Add the .java source files for your plugin to the <tt>src</tt> directory. | ||
| + | # Add any .jar libraries that your plugin requires to the <tt>lib</tt> directory. | ||
| + | # Run <tt>ant</tt> to build your plugin. | ||
| + | # Edit the geWorkbench configuration file to add a directive for your new plugin. | ||
| + | # Run geWorkbench with <tt>ant run</tt> to test your plugin. | ||
| + | # Once satisfied with your plugin, use the provided utility to package your plugin in to a single file for distribution. | ||
Revision as of 13:06, 1 February 2006
The Developer Kit is a self-contained package that facilitates the process of developing plugins for geWorkbench.
Using the Developer Kit
The Developer Kit is available as a .zip file. Unzip it in to a directory of your choice, then follow the instructions below to create a geWorkbench plugin.
The high-level steps for creating, testing and releasing a plugin are as follows:
- Edit the provided Apache Ant build script to specify the name of your plugin.
- Add the .java source files for your plugin to the src directory.
- Add any .jar libraries that your plugin requires to the lib directory.
- Run ant to build your plugin.
- Edit the geWorkbench configuration file to add a directive for your new plugin.
- Run geWorkbench with ant run to test your plugin.
- Once satisfied with your plugin, use the provided utility to package your plugin in to a single file for distribution.
