This will also work for a recursive hash of all files in the current directory or subdirectories (thanks to my sysadmin!):
md5sum $(find . -name '*.jar') > result.txt
The above will mean "./" for the file name (without including the path).
Using the -exec clause from mux adds â*â to the file name (again, without a path).
The specified order of the files also differed between them, but I can not guarantee to say exactly why, since I am a complete noob for bash scripts.
Edit: Forget about the above with respect to the preliminary and complete path, which was based on my experience running remotely at HPC. I just ran the sysadmin sentence in my local windows window using cygwin and got the full path by adding "*. /". I need to use some other fiction to flush the inconsistent path and append to simplify the comparison. In short, YMMV.
source share