> 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.
 >
 > -Alan
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).

Andrejus

Reply via email to