Closed pieterbreed closed 8 months ago
Looks like there is now leiningen preinstalled to action runners. And it is 2.11.1 https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md?plain=1#L89
It is taking precedence over executable installed by this action. Good news — this is fixable. I'll release a new version in a few days. As a workaround you can use full path to installed leiningen binary $LEIN_HOME/bin/lein
as an executable for your task
Hi @DeLaGuardo , thank you for the response and willingness to supply a fix. Unfortunately the work-around is not effective. It still finds and uses the OS-installed leiningen uberjar when invoked like this.
Run cd clj; echo LEIN_HOME=$LEIN_HOME; DEBUG=true $LEIN_HOME/bin/lein test
cd clj; echo LEIN_HOME=$LEIN_HOME; DEBUG=true $LEIN_HOME/bin/lein test
shell: /usr/bin/bash -e {0}
env:
JAVA_HOME: /opt/hostedtoolcache/Java_Corretto_jdk/17.0.10-7.1/x64
JAVA_HOME_17_X64: /opt/hostedtoolcache/Java_Corretto_jdk/17.0.10-7.1/x64
LEIN_HOME: /opt/hostedtoolcache/Leiningen/2.10.0-12-3/x64
LEIN_HOME=/opt/hostedtoolcache/Leiningen/2.10.0-12-3/x64
Leiningen's classpath: /usr/local/lib/lein/self-installs/leiningen-2.11.1-standalone.jar
Right, I just realise that there is LEIN_JAR env variable that points to the exact path to installed leiningen executable. https://github.com/DeLaGuardo/setup-clojure/actions/runs/7832883060/job/21372587378#step:3:115
For some reason unsetting this var doesn't fix the issue. But I confirm that 2.9.1 leiningen works. Proper fix for newest versions will take a day to be merged.
@pieterbreed should be fixed by 12.4 Please update and let me know if it doesn't work for you
Fixed the issue, thank you for the quick turn-around. 👍
I'm impacted by leiningen 2.11.0 breaking some plugins, and need to force lein
2.10.0
for now.NOTE: This issue is not about the classpath for my project. The issue is the classpath from which the leiningen jar is found.
Here is my github actions configuration:
The output shows like this:
so far so good... then
Kindly note the line reading
Leiningen's classpath
, showingleiningen-2.11.1-standalone.jar
.As a result, I'm still impacted by the bug in lein's 2.11.1 version.