-- integration tests now write out mismatches file, which this script reads in, walks the file system to find files with these md5s, and updates them in the files.
-- Should be run like: python private/python/updateMD5s.py integrationtests/md5mismatches.txt public/java/test
-- Note that before using this code you should really commit your code for safety
-- Note also that you ***MUST*** review the differences before running this code. It's not ok to just update md5s willy-nilly
-- Doc from the code:
Update the MD5s across multiple files.
The first argument is the database of MD5 updates produced automatically by the
integrationtests, which lives in integrationtest/md5mismatches.txt.
The second (and more) argument(s) is the path to the source directory containing the java / scala
code with md5s to update. This program crawls that directory looking for .java
and .scala files to update, id's those with MD5s in the md5mismatches.txt files and
updates these files.
It is highly recommended that you commit your code before updating the MD5s to ensure
that if things go wrong with this script that you don't lose any work.
|
||
|---|---|---|
| licensing | ||
| protected/java/src/org/broadinstitute/sting | ||
| public | ||
| settings | ||
| .gitignore | ||
| build.xml | ||
| ivy.xml | ||