Ooops... don't send personal eMails when drunk!
-----Original Message-----
From: Ross Gardler [mailto:[EMAIL PROTECTED]
Sent: 19 September 2008 21:24
To: user@forrest.apache.org
Subject: Re: Using plugins in local dir
Pablo Barrera wrote:
> Hello
>
> I have modified a plugin and I want to install it in my site project.
Do you really want to fork this code? That gives you the maintenance
headache of managing it in the future. Much better would be to propose
your modification as a contribution to the Forrest project where any
future changes to the plugin will be done in a way that will not break
your own modifications.
Of course, if these changes are highly local to your site and not of
interest to the wider community then you may need to maintain your own
version.
> If I have understand it correctly, according to this [1] I should copy
> the whole directory to MYSITE/plugins and modify my forrest.properties
> file as
>
>
project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whitebo
ard/plugins,/export/forrest_plugins
That is just an example, the full text of the paragraph says:
"If you have a collection of local plugins you would like Forrest to use
then you need to add the directory to this property. For example:
project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whitebo
ard/plugins,/export/forrest_plugins"
The important part being. This is not as clear as it could be, a better
phrasing is:
"If you have a collection of plugins in a local directory, such as
'export/forrest_plugins' then you need to add that directory to this
property. For example:
project.required.plugins.src=${forrest.home}/plugins,${forrest.home}/whitebo
ard/plugins,/export/forrest_plugins"
> Forrest uses the old version of the
> plugin instead of the new one, located on MYSITE/plugins. I know this
> plugin should work, because when I move the folder into the forrest code
> (the default location for the plugins) I obtain the desired output. Am I
> missing something here?
Are your plugins in /export/forrest_plugins, that is where you have told
Forrest to look for them.
If yes...
This is now a different plugin, have you changed the name of the plugin?
If not then Forrest will stop looking for it once it finds a copy, with
the property setting you have aboe this means it will find the one in
Forrest first.
I ask again though, are you sure you want to fork this plugin?
Ross
