Please note that the Plugin system has been upgraded to allow versioned
plugins.
You need to do a couple of things with your plugin:
a) add some properties to your build file (see any of the Forrest
plugins for an example).
b) make at least two versions available, the first is a versioned copy
with the name PLUGIN_NAME-VERSION_NUMBER.zip, this should appear in a
subdirectory with the name of the Forrest version number that your
plugin has been tested in. Secondly, you should make an unversioned copy
of the plugin available. This will always be the latest version, and may
be a development release. This version is used as a fallback if no other
suitable plugin can be found (or it can be specified if people like to
live on the cutting edge).
For example, if version 0.1 of your plugin is tested in 0.7 and 0.8
versions of Forrest and 0.2-dev is tested only in 0.8 then you should
should have a download site with:
PLUGIN.zip (this is version 0.2-dev, the latest version published)
0.7/PLUGIN-0.1.zip
0.8/PLUGIN-0.1.zip
0.8/PLUGIN-0.2-dev.zip
NOTE that this need to duplicate plugin versions across directories will
be removed in a future version of Forrest.
For those using the deploy target of the build scripts this directory
structure will be built automatically for you.
Ross
