From dev-return-12827-apmail-forrest-dev-archive=forrest.apache.org@forrest.apache.org Wed Oct 20 04:24:22 2004
Return-Path:
Delivered-To: apmail-forrest-dev-archive@www.apache.org
Received: (qmail 49124 invoked from network); 20 Oct 2004 04:24:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur-2.apache.org with SMTP; 20 Oct 2004 04:24:22 -0000
Received: (qmail 58702 invoked by uid 500); 20 Oct 2004 04:24:20 -0000
Delivered-To: apmail-forrest-dev-archive@forrest.apache.org
Received: (qmail 58578 invoked by uid 500); 20 Oct 2004 04:24:19 -0000
Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
list-post:
Reply-To: dev@forrest.apache.org
Delivered-To: mailing list dev@forrest.apache.org
Received: (qmail 58562 invoked by uid 99); 20 Oct 2004 04:24:18 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from [68.230.241.34] (HELO fed1rmmtao05.cox.net) (68.230.241.34)
by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 19 Oct 2004 21:24:17 -0700
Received: from [192.168.0.3] (really [68.109.82.172])
by fed1rmmtao05.cox.net
(InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP
id <20041020042414.PDSO3459.fed1rmmtao05.cox.net@[192.168.0.3]>
for ; Wed, 20 Oct 2004 00:24:14 -0400
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <1098232936.4222.52000.camel@ighp>
References: <0ABB57CE-DADD-11D8-8DCA-00039385397E@medata.com> <1090396294.1666.65459.camel@ighp> <959D583A-DB23-11D8-8DCA-00039385397E@medata.com> <1090478385.1666.65952.camel@ighp> <71A6B550-DBF3-11D8-90B1-00039385397E@medata.com> <1090564098.1667.67375.camel@ighp> <78D5CBC0-E182-11D8-A85F-00039385397E@medata.com> <599A46F4-E23A-11D8-B3AB-00039385397E@medata.com> <8C2FD019-E242-11D8-B3AB-00039385397E@medata.com> <410A8D7B.9030203@brondsema.net> <410D53A3.8060702@brondsema.net> <65E128D6-E4B7-11D8-BA09-00039385397E@medata.com> <41101B0D.9040408@brondsema.net> <1EC1B9E7-2193-11D9-9F59-00039385397E@medata.com> <95175156-21EC-11D9-B68A-00039385397E@medata.com> <1098232936.4222.52000.camel@ighp>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id:
Content-Transfer-Encoding: 7bit
From: Clay Leeds
Subject: Re: xml-fop Build Failed
Date: Tue, 19 Oct 2004 21:24:06 -0700
To: dev@forrest.apache.org
X-Mailer: Apple Mail (2.619)
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
On Oct 19, 2004, at 5:42 PM, David Crossley wrote:
> 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.
Glad you asked the question as it appears we (the FOP Team) need to
either update our Doc Mgmt page, or temporarily 'double' update the web
site manually: 1) vi over SSH updating of HTML; 2) xdocs/*.xml.
Speaking of which, it sounds like Apache Forrest-0.6 is not yet live on
the server which serves .
I don't understand what you meant when you said 'I wondered that a
while ago, but you must have missed my question.' Wasn't your question:
David Crossley wrote:
> Can you tell me how you currently update the FOP website.
I thought I answered this question when I said:
> 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.
In other words, until I get the xdocs/ back in the running, we aren't
updating our site unless I manually edit the files using vi. If
necessary, I could do your suggestion below, although I'll have to
reapply any changes to the 'working' xdocs/*.xml files (which isn't
really that big a deal).
Was there another question you had that I didn't answer? :-)
David Crossley wrote:
>>> 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
Yes that will. What is prohibiting that? Is there anything I
(we--either the FOP Team or someone else from the Forrest Team) can do
to help?
BTW, thank you for your attention on this issue. I look forward to
resolving it, and with the help of you and the rest of the Forrest Team
it doesn't seem like too much of a challenge!
Web Maestro Clay
p.s. I hope you don't mind that I married this issue with our previous
issue on the dev list, but I figured I'd like to complete 'both'
issues, and I'd rather hash this out on the dev@ list. It's my feeling
that this is more dev-related anyway.
--
Clay Leeds -
Webmaster/Developer - Medata, Inc. -
PGP Public Key: