forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: xml-fop Build Failed
Date Wed, 20 Oct 2004 00:42:17 GMT
Clay Leeds wrote:
> 
> 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).

I see. I wondered that a while ago, but you must have
missed my question. I would suggest going to the manual
build method that i described below for "xml-commons".
It could be a long time before we can update the Forrestbot.
We are waiting for one of the new Apache servers to come
on-line.

> MY CURRENT PLAN TO UPDATE xml-fop
> =================================
> 1. do a fresh cvs checkout of xml-fop
> 2. extract the xml-fop_new.zip 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 xml-fop_new.zip
> 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 cvs.apache.org
> > cd /www/xml.apache.org/commons
> > cvs -q update -dP
> 
> The Doc Mgmt page [1] has a forrestbot interface which makes PUBLISHing  
> fairly simple.

Yes, it will be wonderful when we finally get a forrestbot at ASF.

-- 
David Crossley


Mime
View raw message