Re: Differents between 'forrest' and 'forrest run'
Thorsten Scherler wrote: 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 different behaviour. I see the same skins in both. It looks like the pelt skin. ...because you have not defined a view. I got error messages about plugins during the startup of both 'forrest' and 'forrest run'. I did not get these error messages from the forrest seed site below. That is what I mean. I now as well get the pelt skin and not the leather-plugin. I think that i might have found the problem. The forrest.properties had the wrong name for the plugins. --David
Re: Differents between 'forrest' and 'forrest run'
I got error messages about plugins during the startup of both 'forrest' and 'forrest run'. I did not get these error messages from the forrest seed site below. That is what I mean. I now as well get the pelt skin and not the leather-plugin. I think that i might have found the problem. The forrest.properties had the wrong name for the plugins. --David Cheers that you found and fixed that (I blind). :) I just love OS and you guys. :) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Differents between 'forrest' and 'forrest run'
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 fall! Hey you (Pink Floyd)
Re: Differents between 'forrest' and 'forrest run'
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 do to replicate the issue here? Do i just add to those plugins to forrest.properties project.required.plugins and change project.skin? --David
Re: Differents between 'forrest' and 'forrest run'
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.
How come? How can I fix that?
Any ideas?
What do i need to do to replicate the issue here?
Do i just add to those plugins to forrest.properties
project.required.plugins and change project.skin?
project.skin - should get ignored by the plugins! I am still using
skinit pipes but they can now come from pelt.
project.required.plugins- orgleather, org...view, org...
Just do
1) svn up in {forrest}/plugins
2) cd org...leather; ant local-deploy
3) cd org...view; ant local-deploy
4) in e.g. org...view 'forrest' and then 'forrest run'
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.
Now I just did a 'forrest' on a fresh seed where I add both plugins
(like you stated) and it is working just fine (static/dynamic show the
same). It seems only to be a problem in the plugin which is a bummer
because I cannot deploy them. :(
Cheers for your support.
:)
--David
salu2
--
thorsten
Together we stand, divided we fall!
Hey you (Pink Floyd)
Re: Differents between 'forrest' and 'forrest run'
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.
How come? How can I fix that?
Any ideas?
What do i need to do to replicate the issue here?
Do i just add to those plugins to forrest.properties
project.required.plugins and change project.skin?
project.skin - should get ignored by the plugins! I am still using
skinit pipes but they can now come from pelt.
project.required.plugins- orgleather, org...view, org...
Just do
1) svn up in {forrest}/plugins
2) cd org...leather; ant local-deploy
3) cd org...view; ant local-deploy
4) in e.g. org...view 'forrest' and then 'forrest run'
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 like the pelt skin.
Now I just did a 'forrest' on a fresh seed where I add both plugins
(like you stated) and it is working just fine (static/dynamic show the
same). It seems only to be a problem in the plugin which is a bummer
because I cannot deploy them. :(
It breaks for me in both methods ...
---
/svn/asf/forrest/build/plugins/org.apache.forrest.plugin.view/src/documentation/default.fv
(No such file or directory
---
Perhaps you have some un-committed files.
--David
Re: Differents between 'forrest' and 'forrest run'
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 like the pelt skin. ...because you have not defined a view. Now I just did a 'forrest' on a fresh seed where I add both plugins (like you stated) and it is working just fine (static/dynamic show the same). It seems only to be a problem in the plugin which is a bummer because I cannot deploy them. :( It breaks for me in both methods ... --- /svn/asf/forrest/build/plugins/org.apache.forrest.plugin.view/src/documentation/default.fv (No such file or directory --- Perhaps you have some un-committed files. No, actually this default.fv is the last fallback. I forget to copy it over from the old views. I have views defined in my projects that is why I have not seen this error. Cheers for spotting it, I just checked it in. salu2 --David -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Re: Differents between 'forrest' and 'forrest run'
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 different behaviour. I see the same skins in both. It looks like the pelt skin. ...because you have not defined a view. I got error messages about plugins during the startup of both 'forrest' and 'forrest run'. I did not get these error messages from the forrest seed site below. That is what I mean. I now as well get the pelt skin and not the leather-plugin. Now I just did a 'forrest' on a fresh seed where I add both plugins (like you stated) and it is working just fine (static/dynamic show the same). It seems only to be a problem in the plugin which is a bummer because I cannot deploy them. :( It breaks for me in both methods ... --- /svn/asf/forrest/build/plugins/org.apache.forrest.plugin.view/src/documentation/default.fv (No such file or directory --- Perhaps you have some un-committed files. No, actually this default.fv is the last fallback. I forget to copy it over from the old views. I have views defined in my projects that is why I have not seen this error. Cheers for spotting it, I just checked it in. Okay now i see the default view in my forrest seed site doing both 'forrest' and 'forrest run'. Yeah now you can copy this default.fv to your xdocs dir and rename it to the file that should have a new style (view). e.g. index.xml (index.fv) Anyway it would be interesting to know why it is working for a seed but not for the plugins. I have to give now a course, will have a look tonight. cheers for testing it out. :) --David salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
