<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 08/08/2022 14:41, Andrejus Chaliapinas wrote:<br>
<blockquote type="cite" cite="mid:1223874385.1219538.1659966066435@mail.yahoo.com">
<div class="ydp5a264b8ayahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:13px;">
<div dir="ltr" data-setdir="false">Let me elaborate a bit -
recent use case was when 2 jars were exporting same package
(such was fine in old classpath use case, but not anymore for
Java modules case). And challenge was to figure out which
exactly jar needs to be excluded from Java modules resolution
graph to make overall Java Modules validation work and not
lead to a conflict.</div>
<div dir="ltr" data-setdir="false"><br>
</div>
<div dir="ltr" data-setdir="false">Presence of either of those
jars would satisfy obviously compilation, so issue here is not
about compilation itself. With proposed exclude approach it
would be much easier to exclude jar1 - do various
evaluations/tests and if anything failing - switch to jar2.
And do all that yet not touching Maven (other build tool)
dependencies aggregation inside some folder/local repo. And
once reaching point of passing set - adjust later dependencies
in other places.</div>
<br>
</div>
</blockquote>
Have you tried java --validate-modules? This option will scan the
module path split package for other issues so that you get a dump of
all issues.<br>
<br>
-Alan<br>
<br>
</body>
</html>