On Tue, Jul 14, 2009 at 9:21 AM, ant elder <[email protected]> wrote:
> On Sun, Jul 12, 2009 at 11:38 AM, Steve Poole<[email protected]> > wrote: > > I've now got a trial process going which results in a pdf of the API > > javadoc + a cover sheet. Its available here > > > http://hudson.zones.apache.org/hudson/view/Kato/job/org.apache.kato/org.apache.kato$kato.api/ws/target/site/spec/spec.pdf > > > > The front sheet is not pretty (not sure why there are no margins) but > I'm > > sure its fixable, It relies on using a javadoc doclet from > > http://aurigadoclet.sourceforge.net/ Once you've downloaded > > aurigadoclet to your local environment you need to add a property to your > > maven settings file like > > > > Could you explain a bit more about how aurigadoclet is being used? Its > license is GPL which is a dependency license that can't be used by ASF > projects, that may not be a problem depending how its being used but > i'm not sure i quite grok that yet. Is this generation of the javadoc > going to be part of the regular build or distribution process? > Aurigadoclet currently is used to produce the PDF file directly from the javadoc. I am looking into a way to replace it with a non GPL version. I would like to have the spec document generated as part of the regular build process. > > ...ant >
