Uh oh!
There was an error while loading. Please reload this page.
Change resource used for testing resource-response - #548
Conversation
weavejester
commented
Apr 2, 2026
The test you've modified is explicitly checking resources from a jar file are returned as an InputStream, so changing it to check for a File as well defeats the point of the test. What circumstances are you running the tests under that the |
Indeed, great point. This is an quite unique oddball case, as I'm working another Clojure fork like Babashka called Cloffle https://github.com/The-Alchemist/cloffle-clojure), so the files are exploded. I'm using Maybe there's a better way to achieve this goal? |
weavejester
commented
Apr 3, 2026
The test needs a jar file on the classpath. As I'm unfamiliar with your setup, I'm unsure how best to go about solving this. Are all dependencies exploded, or just Clojure core? Could we just use a different resource? |
The-Alchemist
commented
Apr 19, 2026
Just Clojure code is exploded. So we can just check any resource on the classpath. I force-pushed a new change that checks the file |
weavejester
commented
Apr 20, 2026
That seems fine. Can you ensure all lines are under 80 characters and change the commit message to: |
When testing with alternative Clojure implementations the Clojure core namespaces are not guaranteed to be in a jarfile, so change the resource to a pom.properties file, which we know must be in a jar and not on the filesystem (for example, via a Leiningen checkout). Signed-off-by: The-Alchemist <kap4020@gmail.com>
Change resource used for testing resource-response
When testing with alternative Clojure implementations the Clojure core
namespaces are not guaranteed to be in a jarfile, so change the
resource to a pom.properties file, which we know must be in a jar and
not on the filesystem (for example, via a Leiningen checkout).