forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: svn commit: r190919 - /forrest/trunk/whiteboard/plugins/whiteboard-plugins.xml
Date Thu, 16 Jun 2005 16:20:17 GMT
Thorsten Scherler wrote:
> On Thu, 2005-06-16 at 14:01 +0000, wrote:
>>@@ -110,7 +110,7 @@
>>   <plugin name="org.apache.forrest.plugin.internal.view"
>>         type="internal"
>>         author="Apache Forrest Project"
>>-        website=""
>>+        website=""
>>         url=""
>>         version="0.1-dev">
>>     <description>
> Actually not all whiteboard plugins are listed in your commit nor in the
> docu. e.g. viewHelper is missing.

To appear in the plugins index they need to be in the plugins.xml or 
whiteboard-plugins.xml. You never added viewHelper, so it is not there. 
I have not added it myself because I thought there may be a reason for 
it not being present since you had added view (so I assumed you knew you 
needed to do this).

I'm not very happy with the fact that view and viewHelper have created a 
dependency in the plugins. I want to sort this out when we start working 
on views as a community. viewHelper is not really a plugin because it 
doesn't actually do anything on its own. I believe there should be a 
fourth type of plugin, a view plugin. Things like viewHelper.xhtml will 
go into there.

We will still be able to use the same download mechanism it will just 
stop the plugin list getting confused by the viewHelpers. It is this 
reasoning that I thought you had left out the viewHelper plugin.

 > Can it be that we have to publish (ant build) whiteboard plugins as
 > well?

I'm not publishing most of the whiteboard plugins since they are 
unstable and I think it would be better if only developers have access 
to them. Some of them have been published because they were in the main 
plugins directory originally. But none of the new ones have been published.

If you want to publish the docs for them (in order to prevent 404 links 
you can do so with "ant deploy-docs" (I will be doing all plugin and 
docs deployments tomorrow after the release candidate has been built).


View raw message