forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <>
Subject Re: xml-fop Build Failed
Date Tue, 19 Oct 2004 16:33:18 GMT
NOTE: This discussion was moved from a thread on, since similar threads existed on both lists:

Discussion continues below...

On Oct 19, 2004, at 12:21 AM, David Crossley wrote:
> Clay Leeds wrote:
>> David Crossley wrote:
>>> Clay Leeds wrote:
>>>> As you know. I am the "Web Maestro" for the Apache FOP web site. I
>>>> intend to update the web site soon after
>>>>'s forrestbot is updated to Apache Forrest 0.6.
>>> This bit confuses me. I did not realise that any "forrestbot"
>>> new or old is assisting yet with the site.
>>> We do want it to.
>> Actually, I really just want to make certain that when I commit files
>> for 'xml-fop' via, Forrest-0.6 is used to process my
>> xml-fop/src/documentation/content/xdocs/*.xml
> I am still confused. Can you tell me how you currently update
> the FOP website.

With the exception of a couple of 'vi over SSH' changes to the LIVE  
site (xml-site/targets/fop/), the FOP docs have not been updated  
recently. We are in dire need of update.

(skip if this bores you ;-)) I was considered for FOP committer access,  
not for my heretofore non-existent Java coding abilities, but rather  
for my commitment to helping others on the mailing list, and more  
importantly, my numerous comments on improving web site documentation.  
Unfortunately, when I became a committer I discovered that xml-fop's  
xdocs would not BUILD SUCCESSFULLY. I embarked on a campaign to improve  
the situation only to find that Forrest was 'about' to release 0.6  
(this was months ago). I updated xml-fop to meet 0.6 a few months ago.

My hope is that once the xml-fop docs are in a state where I don't have  
to stress that they still aren't updated, I will be able to focus on  
contributing actual Java-code improvements.

And now onto the response to your question.

Instructions for updating xml-fop are on the Development tab's > Doc  
Mgmt page [1]:
1. Developer commits code to FOP repository
2. Forrestbot "refresh". Automatically done every six hours.
    Can be manually refreshed by authorized users at the
    Forrestbot Web Interface.
3. Forrestbot "publish". Always done manually at the
    Forrestbot Web Interface.
4. Automatic Live Site Update every six hours (midnight, 6am,
    noon, 6pm Pacific time).

1. do a fresh cvs checkout of xml-fop
2. extract the file[2] that the Forrest Team helped with
    (NOTE: see [3] for thread, but [2] is the actual xml-fop*.zip file
    for which Dave had a BUILD SUCCESSFUL[4] later in the thread).
4. follow Dave's excellent instructions[4]
5. replace the xdocs/*.xml files (and sub-dir's files) with
    files extracted from
6. manually generate some PDFs as explained in [4]
7. /forrest/
8. I should then receive a BUILD SUCCESSFUL

Unfortunately, I'm getting a java error. I admit that I haven't done  
step 6 yet, but I can live with a BUILD FAILED error if the only errors  
are something I know how to fix.

> For most websites it is entirely a manual operation.
> For example at "XML Commons" we do this:
> *) Edit the source at
> cvs://xml-commons/src/documentation/content/xdocs/*.xml
> *) Generate the site locally with whatever Forrest that
> the project has decided to use.
> *) Commit the HTML/PDF result to cvs://xml-site/targets/commons/
> *) Commit the edited source to
> cvs://xml-commons/src/documentation/content/xdocs/
> To publish the result, we have an automated cron job to
> do 'cvs update'. Otherwise we do it manually with
> ssh
> cd /www/
> cvs -q update -dP

The Doc Mgmt page [1] has a forrestbot interface which makes PUBLISHing  
fairly simple.

>> Also, is there a reason why the first meta tag in all caps? Wouldn't
>> that violate xhtml rules, which, I believe specify all tags should be
>> lowercase (I realize it says HTML 4.01 Transitional... or are we
>> fishing for a PATCH? ;-))?
> No, i think that if we had used an XHTML serializer in the
> forrest sitemap then all would be lowercase. At the moment
> we are still serializing to HTML so it doesn't matter.

Sounds good! Thanks!

> -- 
> David Crossley

I hope this clears things up a bit. As you can see, I'm eager to update  
the FOP web site!


Web Maestro Clay
Clay Leeds - <>
Webmaster/Developer - Medata, Inc. - <>
PGP Public Key: <>

View raw message