Jump to: navigation, search

Tigerstripe Modules Contribution

Revision as of 05:53, 9 April 2010 by Rcraddoc.cisco.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

< To: Tigerstripe Extension Points

  • Full name : org.eclipse.tigerstripe.workbench.base.module

Purpose : Some Tigerstripe modules can be installed as part of the SDK install. Use of this Extension Point allows for a module to be wrapped into an eclipse plugin. This eclipse plugin can be downloaded as part of the build, or from an update site, making the task of maintaining consistency that much easier.

  • Usage : There should only be one contribution of this extension point in any eclipse plugin. There can be multiple contributions.

The extension point has NO attributes. It is effectively a "tag" to say that this eclispe plugin is a module. Note: The extension point does not validate the module itself, so this should be checked before contribution.

  • Example :
<plugin>
  <extension point="org.eclipse.tigerstripe.workbench.base.module">
     <module/>
  </extension>
  ...
</plugin>
  • Conversion :

To make an existing Tigerstripe Model Project into an eclipse plugin that contributes to this point requires the following:

Select the Project and right-click. Choose the option "Export", select "Tigerstripe" -> "Tigerstripe Module" in the opened Wizard and press "Next". Enter appropriate module ID and path to result JAR-file. Make sure that "Export as installable module" checkbox checked.

(Ensure the target file is a .jar)


  • Some important notes :

If the module has already been deployed in your eclipse environment, the tigerstripe base will pick up the LOCAL copy first - ie the "deployed" rather than "contributed" version. If you Un-deploy the LOCAL version, then the Contributed version will take its place. In this context the modules are considered to be the "same" if their model ID match.