Analyse module definitions in Truffle API JARs in Maven and Graal Distribution

[radeusgd]

Summary

It is suggested that these two differ in how 'open' each of them is.
Maybe the Maven distribution is open enough to allow zinc to do its API anaylsis.

Value

We may get rid of the Illegal Access Errors by making sure zinc loads the right version of the JAR, as long as one of them is really more open.

Specification

• Compare the differences between the two JARs
• Make sure which one is used by javac and which one is loaded by sbt / zinc process
• We may also explore the possibility of patching the JAR with more open permissions. (Unnecessary as the Maven version of Truffle is open as necessary, we just have to ensure we use this one).

Acceptance Criteria & Test Cases

• We know about the differences between the JARs
• If one of them is more open, we have tried switching zinc to use it
• If they are not open, we tried patching the JAR manually to make it more open

[radeusgd]

The module-info.class definitions indeed differ in the distributions - Maven exports Truffle modules to everyone, Graal version only to some Graal modules.

[radeusgd]

I added logging available modules and their permissions in zinc.
It indeed uses the closed Graal-distributed truffle-api.

By adding export SBT_OPTS="--upgrade-module-path=truffle-api-20.1.0-maven.jar" to the environment, we can force sbt to use the more open version and succeed with loading the files.