Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin.
How come? How can I fix that?
Any ideas?
TIA
salu2
--
thorsten
Together we stand, divided we
Thorsten Scherler wrote:
Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin.
How come? How can I fix that?
Any ideas?
What do i need to
On Mon, 2005-04-04 at 19:42 +1000, David Crossley wrote:
Thorsten Scherler wrote:
Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin.
Thorsten Scherler wrote:
David Crossley wrote:
Thorsten Scherler wrote:
Hello devs,
trying to deploy the view and leather plugin I found a weird thing
happening:
Doing 'forrest run' brings the site rendered by the plugins, but doing
'forrest' will use the normal skin.
On Mon, 2005-04-04 at 20:41 +1000, David Crossley wrote:
You will see the plugin get rendered by 'forrest' with the pelt skin in
build/site. If you now turn to 'forrest run' instance you find a
complete different skin.
I get different behaviour. I see the same skins in both.
It looks
On Mon, 2005-04-04 at 21:02 +1000, David Crossley wrote:
Thorsten Scherler wrote:
David Crossley wrote:
You will see the plugin get rendered by 'forrest' with the pelt skin in
build/site. If you now turn to 'forrest run' instance you find a
complete different skin.
I get
David Crossley wrote:
David Crossley wrote:
David Crossley wrote:
David Crossley wrote:
Dave Brondsema wrote:
/docs/dev/ nested below /docs/ seems weird. I think it would be better
to host the current stable release at a url like: /docs/0.7/. This
would also permit us to keep documentation for
David Crossley wrote:
I see that many of our plugins, even new ones, are not using
the naming convention.
... snipped from plugins/pluginInfrastructure.html
-
org.apache.forrest.plugin.PLUGINNAME
net.sf.forrestPlugins.PLUGINNAME
In addition the name of the plugin should indicate the
David Crossley wrote:
...
For various reasons, the ASF Board suggested to all projects
to remove authors from sources.
Apache Forrest follows that recommendation. Prior to each
release we scan the code to detect any license issues
and any author tags.
Om that case how about removing the developers
David Crossley wrote:
I started going through the plugins to fix any major issues
before the release.
The /plugins/ area of the website has some old *.zip for the
plugins that have been renamed ...
OpenOffice.org.zip
feeder.zip
htmlArea.zip
text-output.zip
Should i remove them from the
Thorsten Scherler wrote:
If somebody have some spare time and want to help us with the 2nd
generation skinning you can:
I will certainly be helping out, but not until 0.7 is released. Once
that is done this is right at the top of my ToDo list.
Ross
Thorsten Scherler wrote:
On Mon, 2005-04-04 at 20:42 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
If somebody have some spare time and want to help us with the 2nd
generation skinning you can:
I will certainly be helping out, but not until 0.7 is released. Once
that is done this is right
The following comment has been added to this issue:
Author: Ross Gardler
Created: Mon, 4 Apr 2005 5:01 PM
Body:
We also need a summary of plugin functionality in the fresh-site template. This
should be generated when a user runs forrest seed, that is it retrieves the
official
[EMAIL PROTECTED] wrote:
Author: rgardler
Date: Mon Apr 4 15:13:48 2005
New Revision: 160109
URL: http://svn.apache.org/viewcvs?view=revrev=160109
Log:
Deployment of org.apache.forrest.plugin.OpenOffice.org plugin (deployed by
'deploy' target of plugin build script)
Added:
On Mon, 2005-04-04 at 15:52 -0500, [EMAIL PROTECTED] wrote:
My testing turns up not issues, so , once again, thanks for finding
this Rick, I'd gone blind to the problem and it was driving me mad!
No worries! Sometimes all it takes is a fresh pair of eyes. :)
--
Rick Tessner
rick at apache
Ross Gardler wrote:
David Crossley wrote:
I see that many of our plugins, even new ones, are not using
the naming convention.
... snipped from plugins/pluginInfrastructure.html
-
org.apache.forrest.plugin.PLUGINNAME
net.sf.forrestPlugins.PLUGINNAME
In addition the name of the
Ross Gardler wrote:
David Crossley wrote:
For various reasons, the ASF Board suggested to all projects
to remove authors from sources.
Apache Forrest follows that recommendation. Prior to each
release we scan the code to detect any license issues
and any author tags.
Om that case how
Ross Gardler wrote:
Thorsten Scherler wrote:
Ross Gardler wrote:
Thorsten Scherler wrote:
If somebody have some spare time and want to help us with the 2nd
generation skinning you can:
I will certainly be helping out, but not until 0.7 is released. Once
that is done this is right at
18 matches
Mail list logo
