Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [general] Multidoc API of all Commons
Date: Mon, 5 Jul 2004 14:19:11 -0400
Message-ID: <2B64219028BBFF48B3CC957EF10B58FE0521BD@ns1018.SSSI.seagull.nl>
Thread-Topic: [general] Multidoc API of all Commons
Thread-Index: AcRiUSmevYf0gEkeQE6AQaXW0TmZOQAaxCjQ
From: "Gary Gregory" <ggregory@seagullsoftware.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>

This is very nice! I'd personally like to use two views: "Released
Javadoc" and "CVS HEAD Javadoc".

Gary

> -----Original Message-----
> From: Henri Yandell [mailto:bayard@generationjava.com]
> Sent: Sunday, July 04, 2004 22:30
> To: Jakarta Commons Developers List
> Subject: [general] Multidoc API of all Commons
>=20
>=20
> There's been a request on our Wiki for a combined javadoc for a while.
> Part of the request is that we improve our cross-referencing, which I
> think we can easily do, but will take a bit of planning.
>=20
> However, the other part is for a combined front-end (I think). I've
spent
> today hacking around a bit and have come up with:
>=20
> http://www.apache.org/~bayard/multidoc/index.html
>=20
> It's pretty easy maintenance, just give it a bunch of urls. Sorry
> CLI/FileUpload, your javadoc were not in the usual Maven place and I
> haven't tried hunting down correct ones yet.
>=20
> There's still effort needed to ensure we give it the right urls. Many
of
> the ones I quickly generated are in fact for developer javadoc, not
the
> released javadoc. It'd also be nice to modify the format somehow to
get
> more than one version of the same API in there.
>=20
> It's written/hacked in Java. I started to think about it in Perl, but
I
> prefer my Java scraping API too much to have to deal with something
that
> tries to parse HTML. It merely acts as a front end to existing
javadoc; so
> should be easy to grow to cover other parts of Jakarta/Apache
(ECS/ORO?).
>=20
> Currently it's all static, so after a bit of cleaning it would quite
> easily be something that could be hooked up to the Commons site. I'd
like
> to put a dynamic search in there, but that can come later.
>=20
> Anyway, any thoughts and opinions would be gratefully received,
>=20
> Hen
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org