Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 9 Sep 2011 18:57:09 +0000 (UTC)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1911415970.9591.1315594629015.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <314908964.9215.1315591388811.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7620) All profiles should build the
 javadoc
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101484#comment-13101484 ] 

Owen O'Malley commented on HADOOP-7620:
---------------------------------------

They don't take that much time and the developer absolutely should check the result of their changes to the javadoc. Having the equivalent of -DskipTests=true is fine, but by default it should generate the javadoc.

> All profiles should build the javadoc
> -------------------------------------
>
>                 Key: HADOOP-7620
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7620
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Owen O'Malley
>
> Currently, the default profile doesn't generate the javadoc, which gives the developer a false sense of security. Leaving the forrest stuff in the doc profile makes sense.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira