Does the build process add the javadocs to the doc package? Is there a suggested location to place the documentation for modules? I would like to see a process where the module build can update the javadocs (if that is not already done) and where the module documentation can be kept in the module tree (perhaps under site there) and merged into the master site during a build. Has anyone done anything like that? Does anyone have suggestions for how to do this, or objections to doing so?
Claude On Tue, Sep 3, 2013 at 1:51 PM, Andy Seaborne <[email protected]> wrote: > Let's move forwards to a release, even if it means we will want to do > another release quite soon, otherwise we risk a long wait. > > I'd like to get the 2.11.0 done in the next week or so. It'll take more > checking than a maintenance release because of the new modules but we have > already taken a pass over all of them. > > > Going through the new items: > > * New website > > Ready > > * jena-text > > Ready > > * jena-jdbc > > Ready to go? Tests now passing in finite time. > Documentation on the website: > http://jena.staging.apache.**org/documentation/jdbc/<http://jena.staging.apache.org/documentation/jdbc/> > > * jena-spatial > > Not yet in the main build, nor in Fuseki. > Outstanding issue with the dependency on JTS. > > * jena-client > > Not sure of the status here. I don't mind how we proceed: I'm happen to > include it, or to go through a announcement while in Experimental SVN, or > something else. > > * jena-security > > This is now in the main build. > > There is some documentation at... > https://github.com/Claudenw/**JenaSecurity/wiki/_pages<https://github.com/Claudenw/JenaSecurity/wiki/_pages> > > but nothing for the main Jena website. > > Claude - what about at least a placeholder page for jena.a.o? > > ----- > > Anything I've forgotten? > > Andy > > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
