forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: xml-fop Build Failed
Date Fri, 30 Jul 2004 16:07:25 GMT
On Jul 30, 2004, at 8:50 AM, Dave Brondsema wrote:
> On Fri, 30 Jul 2004, Clay Leeds wrote:
>> This problem is more pressing than I thought. For some reason, xml-fop
>> has not been updated by forrestbot[1] for at least two months. I
>> noticed a problem a month ago (I attempted to update the TEAM page
>> after being voted in as a committer). After forrestbot time out
>> problems, I was informed by JeffT that forrestbot.cocondev.org had 
>> been
>> hacked. He was 'awaiting confirmation that the box has been cleanly
>> rebuilt before typing in a passphrase to restart the backend.' Jeff
>> gave me the stop-gap of manually committing my /forrest/ rendered html
>> file(s) (which I may end up doing).
>
> forrestbot.cocoondev.org uses the old forresbot. I'm working on 
> getting an
> ASF forrestbot set up.  But that is really just a webapp front end to
> forrestbot.  All it does is automate the steps (get source, build, 
> commit
> to CVS/SVN, notify).  You can run forrestbot (it's just ant buildfiles)
> locally or do the steps yourself.

Thanks, Dave. That's as I guessed. Now all I have to do, is figure out 
how to achieve a /forrest/ BUILD SUCCESSFUL and everything will be 
great (sort of like dehydrated water... just add water! :-)). I've 
tried reverting to the original sitemap.xmap, but I still receive 
errors for the *.fo & *.svg files scattered around... Since those files 
don't seem to be changing, should I just place 'raw' file1.svg & 
file1.pdf files in the RAW-dir (i.e., manually convert the *.svg & *.fo 
files into *.pdf)?

Web Maestro Clay

p.s. I checked your page... You've been busy! Good stuff. BTW, 
http://csx.calvin.edu/ gives a 403 error.


Mime
View raw message