Explore if module support in sbt would fix the issue

[radeusgd]

Summary

It is conjectured, that the issue is to Graal's special permissions, so adding module support will not fix it.
After analysing Truffle JARs (#432), depending on the results, it may be possible to try recreating the issue we have with simple Java-modules based library, not specific to Graal (although this is just a conjecture).

Value

If it is possible to reproduce the issue with pure Java modules, we will be able file an issue with sbt and possibly wait for better module support by them.
It would also be helpful with any of the possible zinc patches, as a simple, general example would be more convincing.

Specification

It is not clear if it is possible to reasonably reproduce the issue.

• Try creating a simple Java library using the module system, which compiled with sbt breaks it the same way as Truffle

Acceptance Criteria & Test Cases

• The example library is created or we know why it is not possible to do it (ie. it is something Graal-specific)

[radeusgd]

A question has been posted in the zinc's repository regarding support for libraries like Truffle which are distributed in these two variants (the closed and open one) at sbt/zinc#609

[radeusgd]

We may revisit a different solution (instead of the current one based on --upgrade-module-path and the bootstrap task) when full module support is implemented in sbt/zinc, depending on what their implementation will allow for.