Too long starting time for a executable jar build by the uber + jar task

[heskudi]

A executable jar that was created with the uber/jar tasks takes much longer time when starting than the same jar that has been created by leiningen.
It seems obvious that as opposed to leiningen, at first the dependencies of the program have to be compiled before they are executed.
I have found that the original modification data of the dependencies has been lost. As a result, the modification date is now always the copy date with the resulting consequences. Normally, the modification time of the class files is later than that of the clj files.
I myself verified that setting the modification time in boot/pod.clj (unpack-jar) eliminates this issue.