You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2007/02/02 23:36:49 UTC

[Db-derby Wiki] Update of "AddedOrDeletedFilesInDiff" by BryanPendleton

Dear Wiki user,

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

The following page has been changed by BryanPendleton:
http://wiki.apache.org/db-derby/AddedOrDeletedFilesInDiff

The comment on the change is:
Capture Dan's suggestions from mailing list.

------------------------------------------------------------------------------
  
  When you think you are done, issue "svn stat" on your sandbox, and compare the results against the output attached to the JIRA issue.
  
+ === Example: deleting a test file ===
+ 
+ You can perform an svn delete in your own workspace. It only deletes the files locally. Doing this will ensure that an svn stat shows the files as deleted and thus tells the committers what needs to be deleted.
+ 
+ In addition to deleting the obvious files you would need to remove FILENAME.java from any suite file it is in (.runall file). You also need to then run derbyall just to double check that no other test is relying on that class. So the steps to removing an old test are:
+ 
+  1. Remove (svn delete) the test file (.java or .sql) and any support files it has like test_app.properties.
+  2. Remove (svn delete) any master files for that test
+  3. Remove the test from any suite (.runall file) it is in.
+  4. ant clobber ; ant all    (check no build failures)
+  5. run derbyall - check for no (new) failures
+  6. svn diff to create a patch & attach to the jira issue along with the output of svn stat
+