From bccb258d58766c643548e62f0c2e59e9742a562b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Kr=C3=A1l?= Date: Mon, 23 Oct 2023 09:16:51 +0200 Subject: [PATCH] update Java version --- docs/wrapping-dependencies.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/wrapping-dependencies.md b/docs/wrapping-dependencies.md index c21a5c8f0..9a445017a 100644 --- a/docs/wrapping-dependencies.md +++ b/docs/wrapping-dependencies.md @@ -19,12 +19,12 @@ a particular software package by specifying the dependency only on the `. (i.e., without including the "subminor" version, which usually corresponds to a bugfix release). One particular example where this is employed is for `Java`. Since the `2018b` generation of -the [Common toolchains][common_toolchains], we use a wrapper for `Java` (e.g., `Java/1.8`), rather than -depending on a specific version (e.g., `Java/1.8.0_181`): +the [Common toolchains][common_toolchains], we use a wrapper for `Java` (e.g., `Java/17`), rather than +depending on a specific version (e.g., `Java/17.0.6`): ``` python -# specify dependency on Java/1.8 "wrapper", rather than a specific Java version -dependencies = [('Java', '1.8', '', SYSTEM)] +# specify dependency on Java/17 "wrapper", rather than a specific Java version +dependencies = [('Java', '17', '', SYSTEM)] ``` This has a couple of advantages: