You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Ross Gardler (JIRA)" <ji...@apache.org> on 2006/09/11 11:24:22 UTC

[jira] Commented: (FOR-533) Auto Generate plugins.xml entry

    [ http://issues.apache.org/jira/browse/FOR-533?page=comments#action_12433806 ] 
            
Ross Gardler commented on FOR-533:
----------------------------------

There is a problem with this approach (from the user mailing list):


>> when i type "forrest available-plugins" i can see the required version 
>> for a plugin.
>> i'm running 0.7 version and there almost all plugins required 0.8 
>> version. is taht really true?
> 
> 
> This appears to be a problem with the generation of the plugins index. 
> It appears the 0.7 plugins index is showing the plugins for 0.8. We need 
> to make it so that the index only includes plugin version up to the 
> version number for the index being generated. That is, there should be 
> no 0.8 versions appearing on the 0.7 index page.
> 
> It appears that we missed this when creating the versioned pages.

I'm rushing again... 

The above described problem is not the one I am describing, although they are related. The index page on the website suffers the same problem, i.e. 0.8 plugins appearing on the 0.7 index.

It looks like we need to keep a versioned copy of plugins.xml - attaching these comments the relevant JIRA issue.


> Auto Generate plugins.xml entry
> -------------------------------
>
>                 Key: FOR-533
>                 URL: http://issues.apache.org/jira/browse/FOR-533
>             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.
-
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