<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 21/07/2022 14:24, Andrejus Chaliapinas wrote:<br>
<blockquote type="cite" cite="mid:2024878946.190573.1658409893388@mail.yahoo.com">
Hi,
<div><br>
</div>
<div>While dealing with long list of Jar dependencies for complex
Maven project and trying to resolve some of Java Modules
conflicts - I'm finding that sometimes it could be useful to
exclude some modules without yet removing actual jar file from
aggregated directory of dependencies.</div>
<div><br>
</div>
<div>In that regards something like --exclude-modules would help
initially to evaluate impact and later allow adjust
build/dependencies resolution logic. What do you think?<br>
<div id="ymail_android_signature"><br>
</div>
</div>
</blockquote>
I don't think this make sense as code will not compile or run if you
dependences are removed. Have you found modules where the author has
included `requires` clauses for modules that aren't actually
required, or maybe you are dealing with a module path with many
automatic modules and your module is being compiled with
--add-modules ALL-MODULE-PATH? <br>
<br>
One option to be aware of is the --limit-modules option [1] but I
suspect it won't be useful to you right now.<br>
<br>
-Alan<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://openjdk.org/jeps/261#Limiting-the-observable-modules">https://openjdk.org/jeps/261#Limiting-the-observable-modules</a><br>
</body>
</html>