<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 23 Apr 2023, at 00:49, Josiah Noel <<a href="mailto:josiahnoel@gmail.com" class="">josiahnoel@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class=""><br class="">
</div>
<div class="gmail_quote" style="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class="">
<div dir="auto" class=""><br class="">
</div>
<div dir="auto" class="">
<div dir="auto" class="">How would this solve the issue? I can't see how having a second module on the same jar/artifact would work for this case. </div>
</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class=""> Here's how I envision it. In Jar Y, we'd have two modules. </div>
<div class=""><br class="">
</div>
<div class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class="">
<div class="gmail_quote">
<div class=""><br class="">
module y {</div>
<br class="">
</div>
exports y.pkgs;</div>
<br class="">
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class="">
<div class="gmail_quote">}</div>
</div>
</div>
</blockquote>
</div>
</div>
<div class="gmail_quote"><br class="">
</div>
<div class="gmail_quote">and in the second module, we would have the SPI impl class</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class="">
<div dir="auto" class="">
<div dir="auto" class=""><br class="">
</div>
</div>
</div>
<div dir="auto" class="">
<div class="gmail_quote">
<div class=""> module y.inject {</div>
requires static x;</div>
provides x.plugin with y.inject.PluginImpl;</div>
<br class="">
</div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class="">
<div class="gmail_quote">}</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Almost. Module y.inject `requires x`, not `requires static x`. If x is not required by any resolved module, there can be no resolved module that `uses x.plugin`.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="gmail_quote">
<div class="">Now say some project adds the X Jar and the Y jar, the modules should resolve and X should service load the SPI from the y.inject module.</div>
</div>
<div class="gmail_quote">
<div class=""> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto" class="">
<div dir="auto" class=""></div>
<div dir="auto" class="">Instead of a second module my gut says that what would solve this is a: <br class="">
</div>
<div dir="auto" class=""> 'provides static'</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">I'd like this too, but I don't think it's gonna happen.</div>
</div>
<input name="virtru-metadata" type="hidden" value="{"email-policy":{"disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"expandedWatermarking":false,"expires":false,"sms":false,"expirationNum":1,"expirationUnit":"days","isManaged":false,"persistentProtection":false},"attachments":{},"compose-id":"3","compose-window":{"secure":false}}" class=""></div>
</div>
</blockquote>
<br class="">
</div>
<div>There’s no need for that if you can get the desired behaviour without it. Since the difficulty is the number of artefacts rather than the number of modules, a multi-module JAR is a more elegant solution, as it doesn’t require a new construct.</div>
<div><br class="">
</div>
<div>— Ron</div>
<br class="">
</body>
</html>