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 2005/12/10 00:09:10 UTC

[jira] Resolved: (FOR-760) resolve plugin default properties from forrest.properties defined plugins

     [ http://issues.apache.org/jira/browse/FOR-760?page=all ]
     
Ross Gardler resolved FOR-760:
------------------------------

    Resolution: Fixed
     Assign To: Ross Gardler

OK so typing the issue made me realise what the solution was, and it was so simple I did it

> resolve plugin default properties from forrest.properties defined plugins
> -------------------------------------------------------------------------
>
>          Key: FOR-760
>          URL: http://issues.apache.org/jira/browse/FOR-760
>      Project: Forrest
>         Type: Bug
>   Components: Plugins (general issues)
>     Reporter: Ross Gardler
>     Assignee: Ross Gardler
>     Priority: Blocker
>      Fix For: 0.8-dev

>
> The new forrest.properties.xml facility that allows plugins to provide configuration options has the potential to break backward compatability in its current guise.
> The problem is that for the defaults to be loaded the plugin list must be provided in forrest.properties.xml, however not all projects have this, certainly not pre 0.8-dev projects.
> All we need to do is iff forrest.properties.xml does not have a setting for requried plugins we default to using the setting in forrest.properties
> I think this only means changing the order in which the config files are loaded, but i don't have the time to check now, hence this issue. (thanks to David pointing this out on IRC)

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