You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Riddley appears to be incompatible with mranderson
It seems that the cause is related to the fact that
both walk.clj and compiler.clj is duplicated which I guess confuses mranderson when it unzips the jar. I am guessing the reason the jar is looks like this is this line in riddley's project file: :java-source-paths ["src/riddley"]
in riddley 0.1.12 (but a similar error is produced in 0.2.0 by mranderson you can view the error here: benedekfazekas/mranderson#44)
This patch fixes the problem reported in issue ztellman#31 where the riddley JAR
would include the source files in the JAR root.
After this change, the JAR contents look like this:
Archive: target/riddley-0.2.0.jar
Length Date Time Name
--------- ---------- ----- ----
229 10-09-2019 20:54 META-INF/MANIFEST.MF
2740 10-09-2019 20:54 META-INF/maven/riddley/riddley/pom.xml
606 10-09-2019 20:54 META-INF/leiningen/riddley/riddley/project.clj
2131 10-09-2019 20:54 META-INF/leiningen/riddley/riddley/README.md
0 10-09-2019 20:54 META-INF/
0 10-09-2019 20:54 META-INF/maven/
0 10-09-2019 20:54 META-INF/maven/riddley/
0 10-09-2019 20:54 META-INF/maven/riddley/riddley/
141 10-09-2019 20:54 META-INF/maven/riddley/riddley/pom.properties
0 10-09-2019 20:54 riddley/
1040 10-09-2019 20:54 riddley/Util.class
9757 10-09-2019 20:45 riddley/walk.clj
495 10-09-2019 20:45 riddley/Util.java
2098 10-09-2019 20:45 riddley/compiler.clj
--------- -------
19237 14 files
ztellman#31.
Riddley appears to be incompatible with mranderson
It seems that the cause is related to the fact that
in riddley 0.1.12 (but a similar error is produced in 0.2.0 by mranderson you can view the error here: benedekfazekas/mranderson#44)
It could be argued that that the uberjar should not look like this. What is the rationale for this and could it be 'fixed'?
The text was updated successfully, but these errors were encountered: