Fork me on GitHub
#depstar
<
2021-09-15
>
Huahai01:09:12

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”}

Huahai01:09:44

shouldn’t it just include whatever in the original jar?

Huahai01:09:57

what’s the rationale for ignore file types?

seancorfield01:09:18

@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.

seancorfield01:09:01

Having a .tar.gz file on the JVM classpath doesn't really make sense to me since the JVM can't use it, right?

Huahai01:09:37

ok, make sense, but it make is difficulty to package native artifact in releases

seancorfield01:09:43

If it was in a resources folder (and resources was on the classpath), it would be copied just like any other file.

Huahai01:09:19

that’s how Oracle decided to package their graalvm hosted stuff

Huahai01:09:43

i don’t know why they did it, but that’s the way it is

seancorfield01:09:48

You can always use the jar tool directly to add it to the .jar file after you build it.

seancorfield01:09:07

tools.build's uber task would refuse to copy that file too, BTW.

Huahai01:09:09

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,

Huahai01:09:10

which depends on these platform specific tgz files

Huahai01:09:38

this force people to use lein for such use cases

seancorfield01:09:10

You can post on http://ask.clojure.org for tools.build to support that file type and explain what it should do with it.

Huahai01:09:21

sure, thanks

seancorfield01:09:09

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.

Huahai01:09:04

ok, thanks for letting me know,

seancorfield21:09:08

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!