Staff,
Let me get to this before you wake Ross up. ;)
Please detail the change(s) you've made to the forrest.property file,
possibly using diff if you have that utility. Then include the last few
lines of the build where the error message is displayed. That'll help
all of us by supplying with specifics that we can respond to with
specific suggestions on how to fix them.
I can say that, in general, the skin / view / theme is changed by
modifying the forrest.property file, but exactly how it's changed
depends on which skin / view / theme you're trying to use. I can't say
that I fully understand all of the changes, but I'm trying to keep up ;)
-Paul
info wrote:
First of all,
many thanks Ross.
I would like to give you this feedback: the link you sent me is about some
istructions to use for that purpose.
Unfortunately it seams they don't work with the 0.8-dev release.
In fact if you try to change the proprierty file and set a new skin then
you got always an error. It seams the system tries to access the
main\webapp directory without having the right permission.
Please could you help me?
j2world staff
-----Original Message-----
From: Ross Gardler <[EMAIL PROTECTED]>
To: user@forrest.apache.org
Date: Tue, 03 Jan 2006 23:11:26 +0000
Subject: Re: A couple of questions
info wrote:
Hi all,
I'm new to Forrest and I could only made a simple web site using the
default skin (I guess pelt).
Now I woudl like to ask:
1) because I would like to handle the configuration of the skin and
change
skin (i.e. to tigris) how can I do it? I tried according to the
intructions doing install-skin then I gave forrest...but it doesn't
work.
I'm using the 0.8-dev.
http://forrest.apache.org/docs_0_70/your-project.html#skins
2) can I ask someone to list my website among the ones Forrest
powered.
You already made the necessary request on list this morning. You then
followed that up with a private mail to me, in which I stated support
is
not given offlist, but also pointed you to the fact that David made the
necessary change this earlier today. All you need do now is be patient
and wait for a site update.
Ross