#--module-upgrade-path without explicitly adding an argument.

13 messages · Page 1 of 1 (latest)

lean oyster
# 
configurations {
    truffle
}


dependencies {
    truffle "org.graalvm.truffle:truffle-api:23.0.0"
    implementation configurations.truffle.dependencies
    // ...
}
compileJava {
    options.compilerArgs << "--upgrade-module-path=${project.configurations.truffle[0].toURI()}"
}
```I am doing this to make truffle work - however, is there a way to do this in a way that is less hacky.
crystal mulchBOT
#

⌛ This post has been reserved for your question.

Hey @lean oyster! Please use /close or the Close Post button above when you're finished. Please remember to follow the help guidelines. This post will be automatically closed after 300 minutes of inactivity.

TIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here.

river frigate
#

Why would you need the module upgrade path?

lean oyster
#

because I use graalvm, and graalvm also has truffle, but only internally. But the compiler finds the jdk internal truffle before the dependency truffle, which is the truffle that actually exports the relevant modules

river frigate
#

and you want your project to work without GraalVM as well?

lean oyster
#

that I don't really care about

river frigate
#

oh the graal jvm internal one doesn't export stuff?

lean oyster
#

ye

#

internal

image.png
#

dependency

image.png
river frigate
#

Do both modules have the same name?

lean oyster
#

yes