Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <28677958.1183807988907.JavaMail.jira@brutus>
Date: Sat, 7 Jul 2007 04:33:08 -0700 (PDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1466) Clean up visibility and javadoc
 issues in HBase
In-Reply-To: <19184852.1181092405895.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-1466:
--------------------------------

Integrated in Hadoop-Nightly #147 (See [http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/147/])

> Clean up visibility and javadoc issues in HBase
> -----------------------------------------------
>
>                 Key: HADOOP-1466
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1466
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: contrib/hbase
>    Affects Versions: 0.14.0
>            Reporter: Jim Kellerman
>            Priority: Minor
>             Fix For: 0.14.0
>
>
> We (Michael Stack and I) have turned on warnings in eclipse for almost everything.
> Whenever a class is changed, its visibility, method visibility, internal class visibility, etc. should be examined and javadoc that is incorrect or missing parameters, return values or exceptions thrown should be cleaned up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.