Andrew McIntyre wrote:
On Wed, Mar 12, 2008 at 12:03 PM, Dyre Tjeldvoll <[EMAIL PROTECTED]> wrote:
Daniel John Debrunner wrote:
> The last update to the javadoc on the web-site seems to be 22-Feb-2008.
>
> http://db.apache.org/derby/javadoc/publishedapi/
>
> I know there was an issue with javadoc creation, but I thought it was
> fixed.
>
> Where can I look to see what's failing, I couldn't quickly find any
> explanation of how this javadoc appears.
I've been copying the doc builds with a scheduled process on a machine
of mine to people.apache.org using scp. It would be hard to share
failure information publicly because it would mean copying it off the
private machine, and if it's the copy process itself that is broken
then that's not really possible. :-)
I suppose an improvement here would be to have a scheduled process
that check timestamps on the files on people and sends mail if they're
out of date by a week.
But a better solution would be for the DB project to get a Solaris
Zone on zones.apache.org and then we could do the doc build and push
to the website from there, and the process would be accessible and
maintainable by all the Derby committers. Alas, DB has no zone. I've
suggested that we get one before, as it would be useful for other
things like automated build and push of the website. I don't have time
to chase down the details of creating a zone right now, but I'll help
out in some way if I can. An interested party should look here:
http://www.apache.org/dev/solaris-zones.html
I thought it used to require involvement from infra and a PMC vote,
etc., but it looks like that has changed. It now looks like Jean, as
PMC Chair, may have the necessary karma to just go create one,
although she should probably still get the rest of the PMC and
infrastructure involved first.
FWIW, I think that both Kristian and Knut (and possibly others too) are
seasoned zones administrators on their Solaris desktops, and I'm sure
they would be more than willing to help out with the technical aspect,
if required...
Dyre
