Gav.... wrote:
-----Original Message-----
From: Ross Gardler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 20 March 2007 8:29 PM
To: [email protected]
Subject: Re: Site Builds Failing?
Gav.... wrote:
I have not tried this on site-author yet but I have tried to build and
deploy 3 other sites that uses 0.8-dev.
On ALL of them now I get build failed.
X [0] index.pdf BROKEN: master-reference
'book' for fo:page-sequence matches no simple-page-master or
page-sequence-master
This happens on all PDF files.
I'll have a look but if anyone knows already ...
It is almost certainly a problem local to your system since the
forrestbot is not failing.
I just forrest site on site-author and everything is fine, as expected.
What is the best practice people use when they have to bring their site
directories and builds upto date with trunk?
Watch the commit messages for any changes in the seed sites that may
affect your sites.
Keep an eye on status.xml for notes on changes affecting backward
compatibility.
do svn log on the the seed sites and look for any changes you missed
I'm afraid there is no "easy way" if you are using SVN code. In this
case some work was one recently on the PDF handling in dispatcher. Not
sure if that affects you or not.
If they were built from 'forrest seed' or 'forrest seed-sample' and then
all the content .xml files were added, site.xml, tabs.xml etc all altered
etc etc, but then trunk has changed along the way, these sites may now
not be compatible when built again.
This is just a guess at what has happened to my sites.
Is it safe to copy the src/documentation/** directories elsewhere, seed a
new
site and then copy ssrc/documentation/** back again, would that work?
Not always, because, for example, if a new property is created in
forrest.properties you will overwrite this when copying back your own
version.
Ross
