Gav / David,
Where does cli.xconf go for a site outside the forrest tree? I have
it in {project_root}/src/documentation/conf/cli.xconf. The uncommented
area for checksums reads like this:
<checksums-uri>build/tmp/checksums</checksums-uri>
I changed it from build/work because I don't have one (yet). Forrestbot
isn't behaving for me, but that's another message...
I don't see checksums in build/tmp. Do I need to "touch checksums"
there for it to be found? This site is being generated by Forrest v0.7,
does that make a difference?
Thanks!
-Paul
Gav.... wrote:
----- Original Message -----
From: "Gav...." <[EMAIL PROTECTED]>
To: <dev@forrest.apache.org>
Sent: Friday, October 28, 2005 7:35 PM
Subject: Re: speeding up the static build (Was: Roadmap for v2)
|| Sure, we know that there are ways to speed the site
|| build process. Cocoon CLI checksums. There is probably
|| a Jira issue registered for that.
|
| Nothing recent that I can see, I will uncomment out the line
| that reads <checksums-uri>build/work/checksums</checksums-uri>
| in the cli.xconf (site-author ?) , I guess I don't need to do anything
else
| ?
Nothing else needs doing, this works fine.
I did a 'forrest site' to an unchanged site and it took 3:55
I then enabled the checksums and did 'forrest site' again
it took over 4 minutes - during this time I guess the checksums
are at work.
I then did a 'forrest site' again and it took 2:50 and correctly
skipped all files.
This should be enabled by default for a 'forrest site' I'd have thought ?
Anyway, will play with Forrestbot and see if it takes advantage of this.
Gav...
