YADE Client should handle Integrity Hash parameters in log output

Current Behavior

• There is no indication listed in the Target block of the YADE CLI output that integrity hash parameters have been set.
• There is no indication in the CLI output that all files have been successfully checked against their integrity hashes. (Only errors are reported.)
• The number of successful and unsuccessful file transfers is not correctly written to the CLI output in the event of an error:
  • Consider when five files have been found for transfer and the integrity hash for one file is found to be incorrect after two files have been correctly checked and transferred. Transfer of the remaining three files will be aborted and rolled back. However, 3 successful and 2 unsuccessful transfers will be reported.
• See also YADE-370

Example Configuration

• Download the local_2_local_file_complete.xml file from:
  • The JADE Client Command Line Interface - Tutorial 5 - Checking files for completeness
• Follow the procedure described in the first two examples on that page to run transfers with and without an integrity hash mismatch error.

Desired Behavior

• Check integrity hash parameters should be listed in the Target block of the YADE CLI output e.g. after OverwriteFiles.
• An entry should be made in the CLI output after a transfer operation has been completed and all files successfully checked against their integrity hashes.
• The number of successful and unsuccessful file transfers should be correctly written to the CLI output.

See Also

• https://change.sos-berlin.com/browse/YADE-370