Hi all,
I have added MIDAS support to my MITK fork, but since I prefer my fork to
diverge as little as possible from the mainline master, I thought I'd run
by the idea of incorporating the change into MITK itself. The required
change looks something like this:
https://github.com/nocnokneo/MITK/commit/31b760768fb8021e59df37fda44c0a90ef70b508
Though it would need to be rebased against the latest MITK cmake scripts...
My fork is a bit behind.
The change allows test arguments like MIDAS{file1.nrrd.md5} to be used.
When a test target is run then file1.nrrd gets downloaded locally and the
local path to file1.nrrd is substituted for MIDAS{file1.nrrd.md5} when the
test is actually executed. If there are no test argument strings matching
MIDAS{...} then there is no change to the current behavior.
Thoughts?
Regards,
Taylor
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
