hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Hbase/HowToContribute" by JimKellerman
Date Sat, 09 Feb 2008 03:47:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by JimKellerman:

The comment on the change is:
Add Eclipse usage guidelines

    * If a HBase cluster is needed by your test, either subclass {{{org.apache.hadoop.hbase.HBaseClusterTestCase}}}
or use {{{org.apache.hadoop.hbase.MiniHBaseCluster}}}. If you also need to use a !MapReduce
cluster, use {{{org.apache.hadoop.MiniMRCluster}}}.
    * Place your class in the {{{src/test}}} tree.
    * you can run all the unit test with the command {{{ant test}}}, or you can run a specific
unit test with the command {{{ant test -Dtestcase=<ClassName>}}} (For example {{{ant
test -Dtestcase=TestHBaseCluster}}})
+ === Eclipse is your friend ===
+ If you use Eclipse, it can help you find problems before you submit your patch. Here's some
configuration tips:
+ Open Window->Preferences... and open Java->Compiler
+  * Under Errors/Warnings, set all entries to Warning, except for the following which should
be set to Ignore:
+   * __Code style__
+    * Unqualified access to instance field
+    * Undocumented empty block
+    * Non-externalized strings
+   * __Potential  programming problems__
+    * Boxing and unboxing conversions
+   * __Name shadowing and conflicts__
+    * Local variable declaration hides another field or variable
+   * __Deprecated and restricted API__
+    * Forbidden reference (access rules) should be set to Error
+  * Under Javadoc, all categories should be flagged as Warnings for Public members
+ If you can make all the yellow bars at the right of your editor pane, you have very well-formed
Java code.
  == Generating a patch ==

View raw message