Closed jrevels closed 10 years ago
It sounds like Leiningen 2.5 has some breaking changes. What version of Lein-Ring are you using?
You could also try to add the following profile:
:uberjar {:aot :all}
This pull request I've just made should just solve it. In any case, a temporary workaround is to add the following:
:auto-clean false
into project.clj, regardless of whether {:aot :all}
is set or not.
After updating to Leiningen v2.5, I get an error when running
lein ring uberjar
in my project:I had assumed that ring made a main class itself for the handler I provided; is this not what should happen?
If I go to run the generated uberjar using
java -jar
, it returns aInvalid or corrupt jarfile
error.Any thoughts?