-Retaining-origin-file-timestamps-tp5773664p5773994.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h
.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-shade-plugin-Retaining-origin-file-timestamps-tp5773664p5773855.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe
We could remove clj files from the jar altogether. However, the problem is we
don't know if all the clojure dependencies are AOT compiled. So, some of the
clojure files should be compiled on the fly. The problem is when dynamically
compiling clojure files whose class files already exist in the
Hello,
I am currently using maven shade plugin to package a project jar that would
contain some java libraries as well as some clojure libraries. After some
investigation into load time performance issue, I found that maven shade
plugin default behaviour is to re-write or create the files, which
compile it on the fly. For example, if a.clj and a corresponding a.class is
present with equal timestamps then clojure would think that a.clj is newer
and would compile it. This is causing all the clojure files to be compiled
again and thus causing jar load time to increase.
Perhaps just
