Tersus: Creating a custom feature

Creating a custom featureDate: Oct 16, 2007[Remember to update the documentation of Plug-in Development according to this page] If you want to add your own plugins to Tersus, you can either contribute them to the core platform (adding them to the tersus.library plugin), or create an Eclipe feature that you can deploy into Tersus studio:

Follow the instructions for setting up a development environment.

Download the file tersus-extension-feature.zip to your computer (save it an a temporary location)

Import the template plugin and feature : Import->Existing Projects, check 'archive file' and select the zip file 'tersus-extension-feature.zip'

You can rename the project, but note that the references are not updated (you will need to change the names inside the files plugin.xml, feature.xml and MANIFEST.MF files)

Add your plugin models, icons, classes and plugin descriptors to the plugin project.

Add the names of the classes to extension area in the plugin.xml file (an example is included)

If you want to contribute to the palette, update the palette.xml file.

To test (prior to deployment)

Run the ant file (build-library.xml)

Choose Run -> Tersus Studio Test from the main menu

To deploy to a Tersus Studio:

Run the ant file (build-library.xml)

Open File->Export and select 'Deployable Features'

Select your feature name (e.g. my.tersus.extension)

Select 'Archive file' and type the destination file name (e.g. c:\temp\myfeature.zip)

Unzip the content of the creatd archive into target Tersus/Eclipse installation folder (so that the contents of the folders 'features' and 'plugins' are merged with existing content)

Restart the target Tersus Studio

You may need to manually enable the new features using the Eclipse configuration manager (Help->Softaware Updates->Manage Configuration)

To deploy to a stand-alone server

Check out the projects 'tersus', 'tersus.utils', 'tersus.foundation', 'tersus.appserver' , 'tersus.library', 'tersus.docgen' from the Tersus CVS repository

Run the ant file 'build-server.xml' (in your new plugin project)

Copy the 'build' folder from your plugin to the target environment (you may need to refresh the project in the navigator view before you see the 'build' folder)