These are crazy expert methods; must they be public?
do tests survive a moderate beasting?
I was only worried if they might rely on commit-on-close (vs waiting for merges).
I ran distributed beasting for 25 iterations ... only failure was LUCENE-5595 ... I'll commit shortly and let Jenkins chew on it.
Commit 1643891 from Michael McCandless in branch 'dev/trunk'
[ https://svn.apache.org/r1643891 ]
LUCENE-6097: make abort/waitForMerges private
Commit 1643895 from Michael McCandless in branch 'dev/branches/branch_5x'
[ https://svn.apache.org/r1643895 ]
Commit 1643897 from Michael McCandless in branch 'dev/branches/lucene_solr_4_10'
[ https://svn.apache.org/r1643897 ]
LUCENE-6097: mark abort/waitForMerges deprecated
Bulk close after 5.0 release.