you should first glob the files, and then copy those individually. fs/copy doesn't support globs

Hi Borkdude, sorry I must be missing something: I get: (fs/copy (fs/glob "." (str relpath "/lifecycle/*.yml")) (str "working/" relpath "/Lifecycle/ansible/scripts/") ) ^--- No implementation of method: :as-file of protocol: #'http://clojure.java.io/Coercions found for class: clojure.lang.PersistentVector

(doseq [f (fs/glob ...)]
  (fs/copy f dir))

although I guess copy could support a vector in the future

Could you explain the options: I see: (copy src dest {:keys [:replace-existing :copy-attributes :nofollow-links]}) and (copy-tree src dest {:keys [:replace-existing :copy-attributes :nofollow-links], :as opts}) but the second caused an error - which is the right one?

(copy src dest {:replace-existing true :copy-attributes true :nofollow-links true})

Thank you.

Hey @U01FQSYHRCY :) exec only works if this is available: https://github.com/babashka/process/blob/dadcff417675c84dcd32448e22e6270d1555af5d/src/babashka/process.cljc#L559-L563

from a strings output, I can see that the ProcessProperties stuff is not included in our mandrel bb builds, but they exist in the upstream graalvm builds. But I'm not sure why this is the case.

yes, but if you look at that java code there, mandrel supports exec

i think the question is why bb doesn't pick it up?

@U01FQSYHRCY Perhaps they build the uberjar using non-graal and then compile using graal native image

you should build both the uberjar and the native image using the same Graal JDK preferably

(or Mandrel)

export GRAALVM_HOME=/usr/lib/jvm/mandrel17
        lein deps
        script/uberjar
        script/compile

that's essentially what i do

also export JAVA_HOME

and also set the PATH, might also help

will try, thx

doesn't make a difference 😕

can I check from the .jar if it's builtin already?

what is the exact error you're getting with exec?

• 72,405 (65.64%) of 110,314 methods reachable + 72,405 (65.63%) of 110,315 methods reachable

that's the only difference between the two jvm? oO

clojure.lang.ExceptionInfo: exec is not supported in non-GraalVM environments

if #'process/has-exec? is false, then it means that already at compile time the process thing wasn't detected

let's see if i can just patch that check out

you can try to run this in a clj REPL with your mandrel JDK:

(def ^:private has-exec?
  (boolean (try (.getMethod ^Class
                            (resolve 'org.graalvm.nativeimage.ProcessProperties) "exec"
                            (into-array [java.nio.file.Path (Class/forName "[Ljava.lang.String;") java.util.Map]))
                (catch Exception _ false))))

does that return true or false?

false

and (resolve 'org.graalvm.nativeimage.ProcessProperties)?

or just org.graalvm.nativeimage.ProcessProperties for that matter

if that returns false, then that's your answer

nil

perhaps you need the svm jar on your classpath for this to work

but the class is in the graalvm-sdk

hrm

https://mvnrepository.com/artifact/org.graalvm.nativeimage/svm

not sure

-rw-r--r-- 0 0 0 3076 Mar 16 06:42 org/graalvm/nativeimage/ProcessProperties.class

why are you using mandrel again?

because i couldn't compile graalvm on a musl host

ok, now i fiddled it into the classpath

then it's true

now let's see how to make the build scripts use it

so i think the problem is the uberjar classpath doesn't contain it, then it's disabled, and it doesn't help that native-image would include it because nothing uses it

If it helps, we could allow one extra classpath entry via an env var or so?

what happened to the good old days when $CLASSPATH was simply respected. 😄

I don't even remember those days :)

/masterdir/builddir/babashka-1.2.174/bb -e '(babashka.process/exec "ls")'

it works!

niiice

i hacked it into :resource-paths

80% of things i know about java are from a java 1.1 book my dad had, you know 😉

👍

i'll just patch this locally, no need for you to change things

I suppressed most things I knew about Java until I used Clojure ;)

well same

cool