forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: [JIRA] Commented: (FOR-356) multi-user capability (Was: Solaris problem)
Date Tue, 22 Feb 2005 14:10:00 GMT wrote:
> The following comment has been added to this issue:
>      Author: Fabio Rinaldi
>     Created: Tue, 22 Feb 2005 7:42 AM
>        Body:
>>Regarding the first part of the suggestion. That is not possible 
>>at the moment, because 'build clean' would remove it. Perhaps we 
>>should just have an FAQ about mult-user systems. 
> It might be sufficient to add the following line at the end of
> main/
> mkdir ../build/plugins

Sounds like a reasonable workaround.

> Anyway, since the plugins are included in the archive file, it might
> be easier to do:
> mv ../plugins ../build

 > If the above is added at the end of main/, then the process
 > of installation is reduced to two steps (even in a multi-user
 > environment) to be performed by the system administrator:
 > 1. unpack the archive in the directory of choice
 > 2. cd main;

This is not a good solution as not all plugins are distibuted with 
Forrest, nor are all plugins requried by any specific installation. It 
is possible (IMHO it is likely) that a future release of Forrest will 
not include any plugins in the distribution in order to reduce the 
download size.

> This works fine (just tested on a solaris system).
> However, I then tried to remove the pdf plugin, and was expecting
> to receive the usual friendly message about missing plugin when
> creating a site as a regular user. Instead I got the following
> (which is not very helpful):
> /opt/apache/forrest/main/targets/plugins.xml:246: The following error occurred while
executing this line:
> /opt/apache/forrest/main/targets/plugins.xml:249: The following error occurred while
executing this line:
> /opt/apache/forrest/main/targets/plugins.xml:169: The <var> type doesn't support
the "depends" attribute.
> I guess this is the effect of some recent change?

Yes this is a result of a patch I applied earlier today, I was rushing 
and did not do a "build test". I'll fix now.


View raw message