On Jan 3, 2007, at 4:50 AM, Geir Magnusson Jr. wrote:
On Jan 3, 2007, at 3:37 AM, Mark Brouwer wrote:What is the policy at Apache for hosting the generated javadoc for what we call specifications and implementations, as is currently done by Sunat e.g. http://java.sun.com/products/jini/2.1/doc/api/All projects I checked (which was just a sample) have no online Javadocand from the past I can recall some deferred to other parties for hosting the Javadoc.In my experience, we put the Javadoc right on the website. Now, this is stuff I didn't check in, but just generated and "hung" on the website at a designated spot.But it's the javadoc generated from the project source, not the spec javadoc from elsewhere.My personal opinion is that I would like to have the Javadoc online forthe main branch (I believe you call it the trunk) that reflect thenightly builds as well for every latest release, all in a predictable place.Not only is this convenient to point to in discussions and helping out people, it is also essential for those that like to link against thesewhen generating their own Javadoc.Ok. I think the nightly is excessive, but I don't really care either way :)
I think it's useful to have "the latest" whether that's the result of a nightly or whatever, on the main web site.
It's also useful to have a downloadable version of the entire javadoc. This is an easy way to get the whole thing to review offline, whereas the html version can be used as a permlink. See http://db.apache.org/jdo/javadoc.html for an example. I don't claim it's perfect (it isn't automatically built) but it may give some ideas.
Craig
BTW for the Sun people, what will happen with the current hosting of specifications, etc. at http://java.sun.com/products/jini? -- Mark
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
