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-528) Add version control to plugins
Date Fri, 10 Jun 2005 12:00:46 GMT
    [ http://issues.apache.org/jira/browse/FOR-528?page=comments#action_12313260 ] 

Ross Gardler commented on FOR-528:
----------------------------------

Done, I think, but this needs testing before I close this issue.

TESTING
=======

To test the download of versioned plugins you need to specify which version you want in your
forrest.properties file (add '-VERSION_NUMBER' to the plugin name).

The system should try and download the correct version number for your current version of
Forrest. If this is not possible then the system will fall back to downloading an unversioned
copy of the plugin. This will always be the latest version published.

Having no version number in forrest.properties will result in the unversioned (i.e. latest)
copy of the plugin being used.

Forrest will maintain multiple versions of a plugin to allow different sites to use different
versions where necessary.

All behaviour is intended to be backward compatible with existing Forrest sites.

> Add version control to plugins
> ------------------------------
>
>          Key: FOR-528
>          URL: http://issues.apache.org/jira/browse/FOR-528
>      Project: Forrest
>         Type: Improvement
>     Versions: 0.7-dev
>     Reporter: Ross Gardler
>     Assignee: Ross Gardler
>     Priority: Blocker
>      Fix For: 0.7-dev

>
> David Crossley wrote:
> > Ross, are you able to explain what needs to happen with the plugins
> > at release-time. I mean do they all need to have "-0.7" appended
> > to the names of the zip files?
> Blast I forgot that entirely (again!). Yes we need two zipped versions, a pluginname-0.7.zip
and a pluginname-0.8-dev.zip
> The system will then download the correct version for the currently installed version
of Forrest. This will allow us to have a separate release cycle for plugins, if we deploy
from a 0.8-dev version of Forrest then we will have the 0.8-dev zip file.
> However, now I write that down I don't like it because there is no distinction between
a 0.1 version of a plugin for Forrest 0.7 and a 1.0 version of a plugin for Forrest 1.0 (for
example)
> How about I change it to put the plugins in a directory so we have:
> 0.7/plugingOne-0.1.zip
> 0.7/plugingTwo-0.2.zip
> 0.8-dev/pluginOne-0.2-dev.zip
> 0.8-dev/plugingTwo-0.2.zip
> We only allow *-dev plugins in the current *-dev branch of Forrest
> We can worry about the release process for plugins after this release (just get them
out there for 0.7, we can blow the trumpet on subsequent upgrade releases)
> > Do we need to add something to our RELEASE_BOTES.txt file?
> Yes, a section on plugins with a link to the plugins page, I'll add to project-info plugin
> > Does someone need to tweak the build file?
> Yes, leave it with me, I'll implement the above with whatever modifications people think
we need.
> Ross 
> (for follow ups see http://marc.theaimsgroup.com/?l=forrest-dev&m=111821546807300&w=2

-- 
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