On 24/2/2023 11:44, Nils Breunese wrote:
Latest LTS (currently openjdk17) could be reasonable, but ideally the fallback
version should be verified to work. If that implicitly happens on CI, because
there is never a pre-existing Java installation there, then I guess that’s
could be ok, although
Out of curiosity, do the built-from-source openjdk ports have the support for
the oldest macOS releases? In other words, picking, say, Azul, doesn’t support
older OSes as much?
> On Feb 23, 2023, at 4:50 PM, Nils Breunese wrote:
>
> The built-from-source openjdk11 and openjdk17 ports have arm6
The built-from-source openjdk11 and openjdk17 ports have arm64 support. The
openjdk8 port doesn’t though. If you want Java 8 on arm64, you can install
openjdk8-zulu (Azul Zulu OpenJDK) or openjdk8-corretto (Amazon Corretto).
Nils.
> Op 23 feb. 2023, om 22:22 heeft Kirill A. Korinsky via macport
Latest LTS (currently openjdk17) could be reasonable, but ideally the fallback
version should be verified to work. If that implicitly happens on CI, because
there is never a pre-existing Java installation there, then I guess that’s
could be ok, although I personally think it’s good to have expli
Keep in mind that for M1 you probably need zulu JVM.
--
wbr, Kirill
> On 23. Feb 2023, at 21:48, Joshua Root wrote:
>
> 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
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 unnecessar
