"javadoc:javadoc" would probably generate conflicting pages with "javadoc:aggregate" (links might be different, and javadocs would be stored in separate target directories... not sure exactly). Shouldn't be a problem if "javadoc:aggregate" was executed second.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, May 20, 2015 at 12:41 PM, Josh Elser <[email protected]> wrote: > Great, thanks for the feedback! > > I ended up doing javadoc:javadoc and then a javadoc:aggregate. Good to know > I could've done something more concise :) > > I will update the page with those instructions, and not close the ticket > until after you've made a pass. > > > Christopher wrote: >> >> This puts the javadocs in the docs/apidocs folder... but, that's >> probably something we should change. It should go in target/apidocs >> (the default), because that's where plugins/tools probably expect it, >> and we don't bundle it in the docs directory anymore, so there's no >> reason to generate them there. >> >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >> >> >> On Wed, May 20, 2015 at 11:44 AM, Christopher<[email protected]> wrote: >>> >>> Out of date docs. They were removed from the bin tarball awhile back. >>> To generate the javadocs for the site, do the following on the tag: >>> >>> "mvn clean compile javadoc:aggregate" >>> >>> FWIW, I was going to take a look at the releasing.html page to see if >>> there were any edits I could make. This would be a good addition. >>> >>> -- >>> Christopher L Tubbs II >>> http://gravatar.com/ctubbsii >>> >>> >>> On Tue, May 19, 2015 at 10:29 PM, Josh Elser<[email protected]> >>> wrote: >>>> >>>> From http://accumulo.apache.org/releasing.html >>>> >>>> bq. 1. Extract javadocs from binary tarball from the release >>>> >>>> I don't see the Javadocs in the bin tarball for 1.7.0 or 1.6.2. Is this >>>> a >>>> bug or (more) out of date documentation?
