forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <>
Subject [jira] Commented: (FOR-533) Auto Generate plugins.xml entry
Date Wed, 21 Mar 2007 22:34:32 GMT


Ross Gardler commented on FOR-533:

I've done some of the work, the plugins.xml file is now generated from the build.xml file
of plugins in the core and whiteboard plugin directories. This means the documentation page
are dynamically generated.

However, the plugin install system does not use this file. It can't because Forrest is not
running while the plugins are being installed, although it could be since they are not actually
mounted until the first request that uses them. I need to think and/or experiment around this
a little. Longer term we will be using Ivy to resolve the plugins so I'm not sure if it is
worth doing an interim hack.

The other thing that is not currently supported is user defined plugin directories.

> Auto Generate plugins.xml entry
> -------------------------------
>                 Key: FOR-533
>                 URL:
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Plugins (general issues)
>            Reporter: Ross Gardler
>            Priority: Critical
>             Fix For: 0.8-dev
> The information in the plugins.xml file would be better kept in the plugin directory
and added to the plugins.xml file when deployed. This would reduce the amount of duplication
in the plugins config files.
> All the necessary values are now in the plugin build.xml file.
> This change will require that the plugins.xml file be retrieved from the build directory
rather than the plugins directory when building the plugin documentation pages. We will therefore
need a fall back to retrieve this file from the network if it is not currently available -
this can be done with the locationmap

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message