Currently when installing a plugin Forrest attempts to install the most suitable version available. However, it makes no attempt to upgrade plugins when an upgrade becomes available.
We need a target in the buildfile that will upgrade an indicated plugin when possible. This can then (optionally) be used when running Forrest to automatically upgrade plugins.
Description
Currently when installing a plugin Forrest attempts to install the most suitable version available. However, it makes no attempt to upgrade plugins when an upgrade becomes available.
We need a target in the buildfile that will upgrade an indicated plugin when possible. This can then (optionally) be used when running Forrest to automatically upgrade plugins.
Rather than creating a separate build target we should use the existing versioning code:
- versioned plugins are only upgraded on minor (backward compatible) updates
- unversioned plugins are updated whenever the network or source is available and the distibution is newer than the installed plugin (perhaps we need to add the build number to the plugins.xml file so that Forrest does not need ot examine each plugin individually - this will only be possible when the plugins.xml file is gneerated from the plugin build.xml file - see linked issue)
Ross Gardler added a comment - 09/Dec/05 11:58 PM Rather than creating a separate build target we should use the existing versioning code:
- versioned plugins are only upgraded on minor (backward compatible) updates
- unversioned plugins are updated whenever the network or source is available and the distibution is newer than the installed plugin (perhaps we need to add the build number to the plugins.xml file so that Forrest does not need ot examine each plugin individually - this will only be possible when the plugins.xml file is gneerated from the plugin build.xml file - see linked issue)
Improvement
Closed
Major
Upgrading Plugins
- versioned plugins are only upgraded on minor (backward compatible) updates
- unversioned plugins are updated whenever the network or source is available and the distibution is newer than the installed plugin (perhaps we need to add the build number to the plugins.xml file so that Forrest does not need ot examine each plugin individually - this will only be possible when the plugins.xml file is gneerated from the plugin build.xml file - see linked issue)