Support for Java 9 Modules

[yona-asael]

Hi,

Developing a library for my personal proyects, I'm trying to have the best documentation possible and using the most features possible, in sometime during the implementation of the modules an error occurs, here is the error in Gradle.

During an exhausting reasearch, the error is caused by module-info.java not exists in the proyect, checking how implement this via command line and tried some gradle plugins getting the same result, it could be possible someone can add this feature or can possible to contribute to this project to add the support for Modules.

[0x3333]

The problem is that we support 1.8 onwards. We need a Multi-release jar. I'm not well versed in that. Would you be able to write a PR for that?

[yona-asael]

Review the part of Multi-Release jar, researching a little bit about this the best way to do it without a hell of configurations is explained here in this article they mention a plugin but in this case need to be configured manually because the plugin not have the supports for module-info.java

Let me organize my stuff and time to be able for implement this solution.

[0x3333]

I tried using this plugin(https://melix.github.io/mrjar-gradle-plugin/0.1/index.html) but encountered some issues. Unfortunately, I don't have time to research this.

[Xasmedy]

Any news on this?
If creating a Multi-Release jar is too complicated then just create a parallel version that targets Java 9 having the module-info.
The library looks finished anyway, so it would not be a maintenance pain having two different versions.

In case it's still something you don't want to do, target Java 9 or 11 directly, as of 2024 only 28.8% are using Java 8, and they are surely not going to use this library, or if they are, they can remain on an older version (they will not update either way).
If this change is not made, the remaining 71% of Java developers will have issues using this library. And no, disabling modules, a Java feature, is not a fix to this problem.

Edit: for the people that find this comment, this is a good work around, still, this library must support the modules natively either way and this solution must not be a default fix.