Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by MikeKlaas: http://wiki.apache.org/solr/HowToContribute The comment on the change is: rearrange some of the patch info ------------------------------------------------------------------------------ == Generating a patch == A "patch file" is the format that all good contributions come in. It bundles up everything that is being added, removed, or changed in your contribution. - - - == Testing patches == - - You can easily download a patch from JIRA and test it by doing the following: - - {{{ - wget http://issues.apache.org/jira/secure/attachment/12381498/SOLR-563.patch -O - | patch -p0 - }}} - - The address for the patch can be obtained from the issue page, under the "File Attachments" section of the issue. - - If you are on Solaris, you should replace 'patch' with 'gpatch' to use GNU Patch instead. - - Reverting to pre-patch state is one line: - {{{ - svn revert -R . - }}} - - Though this leaves added files, which can be removed with - {{{ - svn st | grep '?' | awk '{print $2}' | xargs rm - }}} - - Another useful trick is to have multiple checkouts of trunk and "bounce" an active changeset from one to another with - {{{ - svn diff | (cd ../otherbranch; patch -p0) - }}} - === Unit Tests === @@ -159, +130 @@ If there's a Jira issue that already has a patch you think is really good, and works well for you -- please add a comment saying so. If there's room for improvement (more tests, better javadocs, etc...) then make the changes and attach it as well. If a lot of people review a patch and give it a thumbs up, that's a good sign for committers when deciding if it's worth spending time on the patch -- and if other people have already put in effort to improve the docs/tests for a patch, that helps even more. + == Working With Patches == + + You can easily download a patch from JIRA and test it by doing the following: + + {{{ + wget http://issues.apache.org/jira/secure/attachment/12381498/SOLR-563.patch -O - | patch -p0 + }}} + + The address for the patch can be obtained from the issue page, under the "File Attachments" section of the issue. + + If you are on Solaris, you should replace 'patch' with 'gpatch' to use GNU Patch instead. + + Reverting to pre-patch state is one line: + {{{ + svn revert -R . + }}} + + Though this leaves added files, which can be removed with + {{{ + svn st | grep '?' | awk '{print $2}' | xargs rm + }}} + + Another useful trick is to have multiple checkouts of trunk and "bounce" an active changeset from one to another with + {{{ + svn diff | (cd ../otherbranch; patch -p0) + }}} + = Helpful Resources = The following resources may prove helpful when developing Solr contributions. (These are not an endorsement of any specific development tools)
