<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Keep in mind that for M1 you probably need zulu JVM.<div class=""><br class=""><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">-- <br class="">wbr, Kirill</div>
</div>
<div style=""><br class=""><blockquote type="cite" class=""><div class="">On 23. Feb 2023, at 21:48, Joshua Root <<a href="mailto:jmr@macports.org" class="">jmr@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Does anyone know why there is no default value for java.fallback? The assumption appears to be that if a port is using this portgroup, it requires Java, since it errors out in pre-fetch if no Java is found. So it seems like having no fallback by default is just causing builds to fail unnecessarily.<br class=""><br class="">If a default fallback is appropriate, what should it be? My initial impression is that the latest LTS openjdk that works on the current OS would be reasonable.<br class=""><br class="">- Josh<br class=""></div></div></blockquote></div><br class=""></div></body></html>