Saxon

Could you please provide an example of something that exhibits the problem, describing the symptoms of failure, where the problem would disappear if we made the proposed change?

Sure. Import this in Eclipse. Hover over the line “import javax.xml.transform.stream.StreamSource;”. It will say “The package javax.xml.transform.stream is accessible from more than one module: , java.xml” and refuse to compile.

Thanks. I'm not sure any of us have Eclipse installed but I guess we should give it a try. It's also true that we haven't started using modules (partly because we still support Java 8 - we got lots of pushback when we shipped a release that didn't work with Java 8).

Note that I do not think that some of you absolutely need to have Eclipse installed. Reading the provided link could hopefully suffice to convince that this dependency is not a good thing to have.

Also note that the example project also don’t use modules.

Fascinating. Thank you. I recently plowed my way through the muddle of xml-apis.jar and somehow failed to notice that they were simply part of the JDK starting at least with Java 8. blush

Good riddance.

Great! Thanks for the prompt update.

Just a minor thing, I’d say that adding exclusions that are unnecessary would obscure your POM for no big gain and be incoherent as you’d then have to exclude every possibly problematic dependency just in case it would in the future pop up in one of your references. Rather exclude only when necessary (and better let the problem visible and solve it in the dependency itself as you just did), I’d say. But it’s possibly a subjective preference. Thanks again anyway.

I meant I excluded it in our build, so that if its absence ever causes a problem, we'll know. I haven't updated the Maven POM to explicitly exclude it.

Perfect, thanks again for the quick reaction.