The Postgres JDBC driver for Java has an Automatic-Module declaration. This means it has a stable module name, but it is still lacking a full module-info. Without a full module-info the driver cannot be used with jlink. Considering Postgres is both a very popular database and my personal favorite, this stinks. Especially since I think there would be non-trivial benefits if a significant portion of libraries worked fully with the module system tooling.
If you can show that your efforts directly led to the desired result you may email me at ethan@mccue.dev and request one of
No Takers
Shading a library - including its contents inside of your own JAR - is a good strategy to eliminate a user-facing dependency. The Maven Shade Plugin is what Maven users use for this. Gradle has similar plugins as well. But to use any of that you also need to be using their respective build tools. There are also CLI tools like Jar Jar Links and Pro Guard which can do similar things.
What I feel is missing is something that performs this same task but is aware of the module system. For all of the options above you need to specially configure them to not get a faulty module info in the end. This is part of why there are so many "Imposter Modules" on Maven Central.
So what I would want is a CLI tool that can "embed" a module into your own, including fixing up service provider usages. Ideally a Maven + Gradle plugin as well but I am personally less interested in that.
If you can show that your efforts directly led to the desired result you may email me at ethan@mccue.dev and request one of
No Takers