Return-Path: X-Original-To: apmail-accumulo-dev-archive@www.apache.org Delivered-To: apmail-accumulo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D12EC1042F for ; Wed, 20 May 2015 16:47:31 +0000 (UTC) Received: (qmail 67648 invoked by uid 500); 20 May 2015 16:47:31 -0000 Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org Received: (qmail 67607 invoked by uid 500); 20 May 2015 16:47:31 -0000 Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list dev@accumulo.apache.org Received: (qmail 67596 invoked by uid 99); 20 May 2015 16:47:31 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 16:47:31 +0000 Received: from mail-yh0-f41.google.com (mail-yh0-f41.google.com [209.85.213.41]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 67A3F1A0504 for ; Wed, 20 May 2015 16:47:31 +0000 (UTC) Received: by yhcb70 with SMTP id b70so14459719yhc.0 for ; Wed, 20 May 2015 09:47:30 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.109.129 with SMTP id s1mr32224986yhg.137.1432140450637; Wed, 20 May 2015 09:47:30 -0700 (PDT) Received: by 10.129.107.215 with HTTP; Wed, 20 May 2015 09:47:30 -0700 (PDT) In-Reply-To: <555CB950.5020703@gmail.com> References: <555BF18E.6080706@gmail.com> <555CB950.5020703@gmail.com> Date: Wed, 20 May 2015 12:47:30 -0400 Message-ID: Subject: Re: Javadocs in binary "release" From: Christopher To: Accumulo Dev List Content-Type: text/plain; charset=UTF-8 One thing I was thinking: I'd prefer people not use build.sh script. I think it kind of discourages lack of understanding what's going on. And... it doesn't really automate things much. The most helpful thing it does is cache your gpg key in your gpg-agent. After that, it's a maven one-liner. What do you think about updating the releasing page to describe what build.sh does, rather than encourage its use? -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, May 20, 2015 at 12:41 PM, Josh Elser 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 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 >>> 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?