Hi Matt, On Fri, 9 Aug 2024 at 20:28, Matt Sicker <m...@musigma.org> wrote: > > Commons libraries are generally self-contained to the point where modularity > isn’t a problem. Things get complicated once you start involving split up > modules like APIs, SPIs, alternate implementations, and reflection-heavy > design patterns that otherwise bypass language rules around member access. > > Perhaps this could be worth discussing with the bndtools maintainers to see > what they’ve done or if they even know this is a problem.
I guess BND could detect calls to `ServiceLoader.load` and add the missing `uses`, however optional dependencies and reflection is much beyond the scope of the tool. If there is a way to have a couple of Maven modules with a `module-info.java` file in `logging-log4j2` and the rest relying on BND, we can keep the JPMS tests in the repo. Otherwise a separate repo seems so much easier. Besides it could test 2.x and 3.x at the same time. Piotr
