Hi all,
Quick one from the Vidocq side (you know the drill by now — strict Java Modules everywhere, no automatic modules, no classpath fallback 🙂).
While wiring up the MicroProfile bricks, we hit the usual annoyance: Jakarta EE API jars are properly modularized these days, but the MicroProfile ones (Config, Health, Metrics, Fault Tolerance, JWT Auth, REST Client, Telemetry, OpenAPI) still don't ship a module-info.java. We ended up repackaging each of them ourselves just to add the descriptor, which works for us but obviously isn't a great story for anyone else wanting real java module support on MicroProfile.
Before opening actual issues/PRs, wanted to float it here first:
Anyone already looked into this / know why it hasn't happened yet? (split packages, Automatic-Module-Name habits people rely on, etc.)
Any objection to us just doing the work?
We're happy to prepare PRs for each spec's API jar with the module descriptors, following whatever naming/exports convention people prefer. Thanks for your feedback and thoughts on this topic
Regards,
Antoine Sabot-Durand
--
You received this message because you are subscribed to the Google Groups "MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microprofile/fc5fd6dd-a1f1-4deb-bd96-ae1232270fcan%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/microprofile/993390e4-5af2-4b6e-bd4c-01a093f783e7n%40googlegroups.com.