Hbase/HowToContribute reverted to revision 57 on Hadoop Wiki

[Apache Wiki <wi...@apache.org>]

Dear wiki user,

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

The page Hbase/HowToContribute has been reverted to revision 57 by stack.
The comment on this change is: Undoing spam.
http://wiki.apache.org/hadoop/Hbase/HowToContribute?action=diff&rev1=61&rev2=62

--------------------------------------------------

  svn co http://svn.apache.org/repos/asf/hbase/trunk hbase-core-trunk
  }}}
  
- If you prefer to use Eclipse for development, there are instructions for setting up SVN access from within Eclipse at [[Hbase/EclipseEnvironment| Working with HBase under Eclipse]]
+ If you prefer to use Eclipse for development, there are instructions for setting up SVN access from within Eclipse at [[Hbase/EclipseEnvironment| Working with HBase under Eclipse]].
  
  Alternatively, if you prefer to use [[http://git.apache.org/hbase.git/|git]], there is a git repository available that mirrors the svn repository. You can retrieve the latest information via git with the following:
  
@@ -40, +40 @@

    * All test class names should start with {{{Test}}}.
    * Use JUnit4 annotations for defining before and after method / class invocations, for example {{{@Before}}}
    * Some classes may still extend {{{junit.framework.TestCase}}} based on the old version of JUnit. If you need to modify these files, migrate them to the JUnit4 convention.
-   * Define methods within your class whose names begin with {{{test}}} and annotate them with {{{@Test}}}, and call JUnit's many assert methods to verify conditions; these methods will be executed when you run {{{mvn test}}}[[http://www.übersetzungsbüro-frankfurt.de .]]
+   * Define methods within your class whose names begin with {{{test}}} and annotate them with {{{@Test}}}, and call JUnit's many assert methods to verify conditions; these methods will be executed when you run {{{mvn test}}}.
    * By default, do not let tests write any temporary files to {{{/tmp}}}.  Instead, the tests should write to the location specified by the {{{test.build.data}}} system property. The {{{org.apache.hadoop.hbase.HBaseTestingUtility}}} class has some utility methods to assist with this.
-   * If a HBase cluster is needed by your test, you should use the {{{org.apache.hadoop.hbase.HBaseTestingUtility}}} to start and stop the cluster. See the {{{org.apache.hadoop.hbase.client.TestAdmin}}} and {{{org.apache.hadoop.hbase.client.TestFromClientSide}}} classes as these are good examples of how the testing utilities can be used[[http://www.xn--bersetzungsbro-berlin-7hcm.net/ .]]
+   * If a HBase cluster is needed by your test, you should use the {{{org.apache.hadoop.hbase.HBaseTestingUtility}}} to start and stop the cluster. See the {{{org.apache.hadoop.hbase.client.TestAdmin}}} and {{{org.apache.hadoop.hbase.client.TestFromClientSide}}} classes as these are good examples of how the testing utilities can be used.
-   * Place your class in the {{{src/test}}} tree[[http://www.übersetzungsbüro-stuttgart.de .]]
+   * Place your class in the {{{src/test}}} tree.
    * You can run all the unit tests with the command {{{mvn test}}}, or you can run a specific unit test with the command {{{mvn test -Dtest=<ClassName>}}} (For example {{{mvn test -Dtest=TestHBaseCluster}}})
    * If you want to quickly build the code without running the tests you can run the command {{{mvn install -DskipTests}}}
    * If your test requires a port, be sure to use an ephemeral port by requesting port 0 in your code and passing the assigned port to the client.
@@ -244, +244 @@

  
   * [[http://www.apache.org/dev/contributors.html|Apache contributor documentation]]
   * [[http://www.apache.org/foundation/voting.html|Apache voting documentation]]
-  * [[http://itshumour.blogspot.com/2010/03/funny-quotes.html|funny quotes]]
-  * [[http://itshumour.blogspot.com/2009/04/fascinating-and-funny-3d-chalk-drawings.html|3d chalk art]]