Bernd Ruehlicke (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-147?page=comments#action_59964 ]Unless you are a committer, you have to submit a patch to the list.
Bernd Ruehlicke commented on DERBY-147:
---------------------------------------
...ehhh ... got a little lost here. Need some info of procedures of "submitting to the trunk"
Shall I just use svn to submit ? and how ?
Any example of how file xyz.java is submitted ?
Sorry - but if I get around those trivial CM issues I can start committing stuff ..
B-)
To prepare a patch, you first use svn to add your file to the appropriate spot. Best to first sync up...
- cd <my_derby_loc>/trunk
- svn update
- svn add java/engine/impl/yadiyadi/xyz.java
- svn propset svn:eol-style native java/engine/impl/yadiyadi/xyz.java
- then you should run the tests (depending on your change, but to be safe, deryball)
- ant all
- set your CLASSPATH env var to include the trunk/classes dir
- cd <a temp/test dir>
- java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall
after you've resolved any test failures (eg. updated relevant ../functionTests/master/*.out files)
you can make the patch.
- svn diff > xyz.diff
Then, mail the xyz.diff to the list. Indicate which tests you've run.
A committer then will pick up the patch, and by using the 'patch' executable apply the deltas from the svn diff file to his/her trunk. After running some tests to double check, they will then commit.
Note: there have been cases where certain email systems mess up the diffs, specifically with enigmail - that's documented on the derby site under contributing with patches...
Myrna
