forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <>
Subject [jira] Commented: (FOR-388) Use plugins in-place if src available
Date Wed, 14 Dec 2005 20:02:45 GMT
    [ ] 

Ross Gardler commented on FOR-388:

I've put a "half-way" solution to this in place. 

Plugins are not used in place, they still need to be deployed. However, during startup Forrest
will now look in the local src directories before trying to download (for unversioned plugins
only, versioned plugins are still downloaded from a remote repository).

Forrestbot installations will now use the local src. This means that our continuous integration
 tests on the zone will use the most recent development version of the plugin, rather than
the most recent release.

Another benefit is that we can now provide a separate zip of plugins and whiteboard plugins
for users with problems with the auto-download mechanism, we will simply direct them to download
the plugins zips and install them in their FORREST_HOME directory.

However, this is not a final solution, it should be considered a hack and removed when we
implement prooper in-place use of plugins. See the commits for this issue to evaluate the
code that will need to be removed.

> Use plugins in-place if src available
> -------------------------------------
>          Key: FOR-388
>          URL:
>      Project: Forrest
>         Type: Improvement
>   Components: Plugins (general issues)
>     Versions: 0.7, 0.8-dev
>     Reporter: Ross Gardler
>     Priority: Critical
>      Fix For: 0.8-dev

> At present Forrest will attempt to download plugins even if they are available in src
form in the local filesystem as part of an SVN checkout.
> Have Forrest mount plugins from designated directories in preference to downloading them
wherever possible (need more than posible location for src plugins as some people may be developing
their own plugins outside of Forrest)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message