Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
Date: Wed, 2 Dec 2009 23:18:01 +0530
Message-ID: <4dc6c9040912020948j5ccbb31wf61da8ee3c5e9124@mail.gmail.com>
Subject: Publishing api docs for Subversion
From: Bhuvaneswaran A <bhuvan@apache.org>
To: general@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Here's a query related to publishing api docs for Subversion project
periodically.

We tend to update the api docs generated using doxygen and java doc on
a nightly basis. We are evaluating a workaround to publish it
periodically. Based on investigation I did so far, most of projects
namely apr, hadoop, jakarta seem to place the apidocs in site/ area,
not updated periodically though. As our use case is to update
periodically, we wouldn't want to commit the auto generated docs in
asf repository often.

Considering these aspects, here's what we are planning to do:
Setup a Hudson job in hudson.zones.apache.org farm that would generate
the documentation using doxygen and javadoc. This can be setup to run
periodically, may be once a day or once a week. Then, push the
documentation files to people.apache.org into one of our accounts
using SCP plugin that is already available in Hudson. We may use a
passphrase/keyfile for authentication.

Please shed some light if this is not the right approach, and/or if
you could suggest a better/alternate approach, that would be helpful.

-- 
Regards,
Bhuvaneswaran A
www.livecipher.com
GPG: 0x7A13E5B0

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org