cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Trivial Update of "HowToContribute" by JaakkoLaine
Date Tue, 17 Nov 2009 03:10:17 GMT
Dear Wiki user,

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

The "HowToContribute" page has been changed by JaakkoLaine.
http://wiki.apache.org/cassandra/HowToContribute?action=diff&rev1=16&rev2=17

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

   1. Check if someone else has already begun work on the change you have in mind in the [[https://issues.apache.org/jira/browse/CASSANDRA|issue
tracker]]
   1. If not, create a ticket describing the change you're proposing in the issue tracker
-  1. Check out the latest version of the source code
+  1. Check out source code
-   * svn checkout http://svn.apache.org/repos/asf/incubator/cassandra/trunk cassandra-trunk

+   * __latest version__: svn checkout http://svn.apache.org/repos/asf/incubator/cassandra/trunk
cassandra-trunk
+   * __0.4 source__: svn checkout http://svn.apache.org/repos/asf/incubator/cassandra/branches/cassandra-0.4
cassandra-0.4
   1. Modify the source to include the improvement/bugfix
    * Verify that you follow Cassandra's CodeStyle.
    * Verify that your change works by adding a unit test.
    * Make sure all tests pass by running "ant test" in the project directory.
   1. When you're happy with the result create a patch:
    * svn add <any new file>
-   * svn diff > CASSANDRA-issuenumber.patch 
+   * svn diff > CASSANDRA-issuenumber.patch
   1. Attach the newly generated patch to the issue and click "Submit patch" in the left side
of the JIRA page
   1. Wait for other developers or committers to review it and hopefully +1 the ticket
   1. Wait for a committer to commit it.
  
  == Testing and Coverage ==
- 
  Setting up and running system tests:
  
   1. install python setuptools, if necessary (`apt-get install python-setuptools`)
@@ -29, +29 @@

  Running the code coverage task:
  
   1. Unzip this one: http://prdownloads.sourceforge.net/cobertura/cobertura-1.9.1-bin.zip?download
-  2. ant codecoverage -Dcobertura.dir=/path/to/cobertura
+  1. ant codecoverage -Dcobertura.dir=/path/to/cobertura
-  3. check build/cobertura
+  1. check build/cobertura
  
  This is also available on Hudson (which updates about once every 24h) here: http://hudson.zones.apache.org/hudson/job/Cassandra/110/cobertura/
  
- 
  == IDE ==
- 
   * [[RunningCassandraInIDEA]]
   * IntelliJ Project Settings:
-    * Main Class: org.apache.cassandra.service.CassandraDaemon
+   * Main Class: org.apache.cassandra.service.CassandraDaemon
-    * VM Parameters: -ea -Xmx1G -Dstorage-config=conf -Dcassandra-foreground
+   * VM Parameters: -ea -Xmx1G -Dstorage-config=conf -Dcassandra-foreground
  
  == Subversion Configuration ==
- 
  Add this to your subversion configuration (~/.subversion/config on unix-style installs)
so that newly added files have the correct auto-properties once committed:
  
  {{{
@@ -58, +55 @@

  *.jar = svn:mime-type=application/octet-stream
  *.bat = svn:eol-style=CRLF
  }}}
- 
  ''Note: for this to work you must enable auto-props by setting'' `enable-auto-props = yes`
''in .subversion/config.''
  
  == Got Git? ==
- 
   * Using git to manage patches during reviews: http://spyced.blogspot.com/2009/06/patch-oriented-development-made-sane.html
   * Uploading and applying patches from JIRA automagically: [[GitAndJIRA]]
  

Mime
View raw message