Java portgroup default fallback?

[Nils Breunese]

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 explicitly set fallback versions.

By the way, I don’t know if MacPorts’ built-from-source openjdk* ports are still actively maintained. I’ve bumped patch updates for the built-from-source ports, because I noticed they were not current, but I lack the knowledge to really maintain those. Therefor I wonder there will be an openjdk21 port after the release in September. There also haven’t been openjdk18 or openjdk19 ports in MacPorts so far.

Please note that I do maintain the other prebuilt Java distributions (Azul Zulu OpenJDK, Eclipse Temurin, Oracle OpenJDK, etc.) in MacPorts, and for instance Java 19 is available via those.

Nils.

> Op 23 feb. 2023, om 21:48 heeft Joshua Root <jmr at macports.org> het volgende geschreven:
> 
> 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.
> 
> 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.
> 
> - Josh