forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-343) Upgrading Plugins
Date Fri, 09 Dec 2005 15:00:08 GMT
    [ http://issues.apache.org/jira/browse/FOR-343?page=comments#action_12359889 ] 

Ross Gardler commented on FOR-343:
----------------------------------

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)

> Upgrading Plugins
> -----------------
>
>          Key: FOR-343
>          URL: http://issues.apache.org/jira/browse/FOR-343
>      Project: Forrest
>         Type: Improvement
>   Components: Plugins (general issues)
>     Versions: 0.7
>     Reporter: Ross Gardler
>      Fix For: 0.8-dev

>
> 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 traget in the buildfile that will upgrade an indicated plugin when possible.
This can then (optionally) be used when running Forrest to automatically upgrade plugins.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message