Dear Wiki user, You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.
The "Chukwa_How_To_Contribute" page has been changed by EricYang: http://wiki.apache.org/hadoop/Chukwa_How_To_Contribute?action=diff&rev1=2&rev2=3 <<Anchor(Documentation)>> ==== Committing Documentation ==== - Hadoop's official documentation is authored using [[http://forrest.apache.org/|Forrest]]. To commit documentation changes you must have Forrest installed and the {{{forrest}}} executable on your {{{$PATH}}}. Note that the current version (0.8) doesn't work properly with Java 6, use Java 5 instead. Documentation is of two types: + Chukwa's official documentation is authored using [[http://forrest.apache.org/|Forrest]]. To commit documentation changes you must have Forrest installed and the {{{forrest}}} executable on your {{{$PATH}}}. Note that the current version (0.8) doesn't work properly with Java 6, use Java 5 instead. Documentation is of two types: 1. End-user documentation, versioned with releases; and, 1. The website. This is maintained separately in subversion, republished as it is changed. @@ -73, +73 @@ Please be sure to include Jira number(s) in the commit message for merge commits. Sometimes developers just put something like "merge -r 4000:4001" in the merge message, which fails to trigger the Jira/Subversion integration, so the Jira doesn't record the branch commit. It is important to link to the Jira number, so that when looking at the Jira it will be clear that this patch has been merged to this branch. - - == Patches that break HDFS and MapReduce == - - In general, the process flow is that Hudson notices the checkin and automatically builds the new versions of the common libraries and pushes them to Nexus, the Apache Maven repository. - - However, to speed up the process or if Hudson is not working properly, developers can push builds manually to Nexus. To do so, they need to create a file in ~/.m2/settings.xml that looks like: {{{ - <settings> - <servers> - <!-- To publish a snapshot of some part of Maven --> - <server> - <id>apache.snapshots.https</id> - <username> <!-- YOUR APACHE SVN USERNAME --> </username> - <password> <!-- YOUR APACHE SVN PASSWORD --> </password> - </server> - <!-- To publish a website of some part of Maven --> - <server> - <id>apache.website</id> - <username> <!-- YOUR APACHE SSH USERNAME --> </username> - <filePermissions>664</filePermissions> - <directoryPermissions>775</directoryPermissions> - </server> - <!-- To stage a release of some part of Maven --> - <server> - <id>apache.releases.https</id> - <username> <!-- YOUR APACHE SVN USERNAME --> </username> - <password> <!-- YOUR APACHE SVN PASSWORD --> </password> - </server> - <!-- To stage a website of some part of Maven --> - <server> - <id>stagingSite</id> - <!-- must match hard-coded repository identifier in site:stage-deploy --> - <username> <!-- YOUR APACHE SSH USERNAME --> </username> - <filePermissions>664</filePermissions> - <directoryPermissions>775</directoryPermissions> - </server> - </servers> - </settings> - }}} - - After you have committed the change to Common, do an "ant mvn-publish" to publish the new jars. - - As a security note, since the settings.xml file contains your Apache svn password in the clear, I prefer to leave the settings file encrypted using gpg when I'm not using it. I also don't ever publish from a shared machine, but that is just me being paranoid. :) - == Dialog == Committers should hang out in the #chukwa room on irc.freenode.net for real-time discussions. However any substantive discussion (as with any off-list project-related discussion) should be re-iterated in Jira or on the developer list.
