<html><head></head><body><div class="ydpa43f3cf5yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false"><div dir="ltr" data-setdir="false"> <div>> 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</div><div><br></div><div>Yes, that was my starting point, i.e usage of --validate-modules. But seeing outcome of it for complex dependencies set led to this my proposal actually. Cause validate shows conflicts, but elimination of them takes effort via build tooling configs. And much easier would be initially to evaluate runtime outcome via flexible exclusion capability (i.e. in a way we have for Maven dependencies exclusions for example).<br></div><div><br></div><div dir="ltr" data-setdir="false">Andrejus</div><div dir="ltr" data-setdir="false"><br></div></div></div></div></body></html>