Date: Thu, 26 Feb 2026 17:35:01 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 293467] Mk/Uses/java.mk: add support for JAVA_VERSION=default and JAVA_VERSION=latest Message-ID: <bug-293467-8522-3nas2imVYN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-293467-8522@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293467 --- Comment #4 from Dmitry Marakasov <amdmi3@FreeBSD.org> --- I'm generally against any logic which relies on which ports are installed - this makes behavior inconsistent between different port install orders and between ports and packages, and is still inconsistent to how we handle other ecosystems (and that we do by pinning exact version of e.g. python). In fact, while my `JAVA_VERSION=default` equals to `JAVA_VERSION=${JAVA_DEFAULT}+` to stay closer to status quo where `X+` are used in most ports, IMO it would make more sense to pin specific version (`JAVA_VERSION=${JAVA_DEFAULT}`) as long as `JAVA_DEFAULT` is being reliably kept up to date. That said, it doesn't look that these patches are conflicting - my patch is about choosing a version range (effecively limiting it from below), and a patch from 289858 is about picking a version in that range. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293467-8522-3nas2imVYN>