This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-15
Channels
- # announcements (51)
- # beginners (65)
- # calva (44)
- # cider (6)
- # clara (3)
- # clj-kondo (30)
- # cljsrn (5)
- # clojure (63)
- # clojure-australia (7)
- # clojure-dev (7)
- # clojure-europe (43)
- # clojure-gamedev (1)
- # clojure-nl (6)
- # clojure-uk (7)
- # clojurescript (51)
- # conjure (1)
- # cursive (9)
- # datascript (16)
- # datomic (14)
- # depstar (20)
- # events (1)
- # exercism (17)
- # figwheel-main (6)
- # fulcro (9)
- # graphql (3)
- # gratitude (2)
- # honeysql (4)
- # jobs (7)
- # leiningen (3)
- # lsp (107)
- # meander (7)
- # minecraft (3)
- # off-topic (16)
- # other-languages (4)
- # pathom (4)
- # pedestal (26)
- # practicalli (4)
- # re-frame (3)
- # reitit (7)
- # remote-jobs (1)
- # shadow-cljs (26)
- # tools-deps (67)
- # vim (19)
- # vscode (1)
depstar ignore native files needed {:warning “ignoring unknown file type”, :path “/home/hyang/.m2/repository/org/graalvm/nativeimage/svm-hosted-native-darwin-amd64/21.1.0/svm-hosted-native-darwin-amd64-21.1.0.tar.gz”}
@huahaiy It knows what to do with .jar
files (explode them and copy their contents) and directories (recursively copy their contents) but doesn't know what to do with other things on the classpath.
Having a .tar.gz
file on the JVM classpath doesn't really make sense to me since the JVM can't use it, right?
If it was in a resources
folder (and resources
was on the classpath), it would be copied just like any other file.
You can always use the jar
tool directly to add it to the .jar
file after you build it.
tools.build
's uber
task would refuse to copy that file too, BTW.
that’s unfortunate, because it makes it impossible to ship code that depends on GraalVM specific APIs, i know not a lot of people do that,
You can post on http://ask.clojure.org for tools.build
to support that file type and explain what it should do with it.
tools.build
's uber
task is almost at parity with depstar
and will soon exceed it, at which point I shall sunset depstar
and recommend people switch to tools.build
.
With the v0.4.0 release of tools.build
supporting conflict handlers, and the availability of this Log4j2Plugins.dat
conflict handler, I plan to sunset depstar
and encourage everyone to use tools.build
instead. Happy to discuss in more detail here!