openjdk@17 を Homebrew, apt, apk, chocolatey, MacPorts, Nix, winget でインストール

プロジェクトリンク

• ホームページ
• リポジトリ
• 上流ドキュメント
• パッケージマネージャページ

コマンドとエイリアス

ローカルパッケージデータベースに実行可能エイリアスは見つかりませんでした。

プロジェクトの歴史

JDK 17 was produced through the OpenJDK JDK Project, whose long-running goal is to ship open-source reference implementations of the Java SE Platform on a strict six-month feature-release cadence. The release was specified by JSR 390, tracked through the JEP process, and delivered using the JDK Release Process.

The release closed a four-year gap from the previous LTS line, JDK 11, and accumulated language, VM, library, and platform work that had been previewed or incubated across intervening releases. Its feature list includes sealed classes, strong encapsulation of JDK internals, a macOS/AArch64 port, a new macOS rendering pipeline, context-specific deserialization filters, and incubating Foreign Function & Memory and Vector APIs.

採用の歴史

The OpenJDK release page identifies JDK 17 as a long-term-support release from most vendors. That status made it a practical migration target for organizations that skipped non-LTS releases after Java 11, and it explains why package managers keep versioned formulae such as openjdk@17 beside newer JDK lines.

JDK 17 also mattered because it tightened boundaries around unsupported internal APIs. Strong encapsulation of JDK internals moved many applications and libraries from permissive legacy access toward explicit supported APIs or deliberate command-line opens, making the release a compatibility checkpoint for the Java ecosystem.

使われ方

Developers use the package as a full JDK rather than only a runtime: it provides java, javac, jar, javadoc, jshell, jlink, jpackage, Java Flight Recorder tooling, and diagnostic tools such as jcmd, jmap, jstack, and jstat. In practice it is installed to compile Java code, run application servers and build tools, create custom runtime images, inspect production JVMs, and match an LTS target in CI.

For package consumers, openjdk@17 is valuable because it pins the toolchain to a stable Java language and class-library level. That matters for Gradle/Maven builds, language-server setups, container images, and projects whose dependencies certify against Java 17 rather than a moving latest-JDK target.

パッケージ好きにとっての重要性

OpenJDK 17 is a package-manager anchor: it is old enough to be a compatibility baseline and new enough to include the post-Java-9 module-era JDK shape. Its formula preserves a vendor-neutral GPL-with-Classpath-exception build of the Java toolchain while newer OpenJDK formulae continue to advance.

The package is also a reminder that language runtimes often need versioned slots. A single unversioned JDK package cannot serve every build, because bytecode targets, compiler behavior, preview/incubator APIs, security updates, and vendor LTS windows all affect reproducible builds.

タイムライン

• 14 September 2021: JDK 17 reached General Availability as the Java SE 17 reference implementation.
• JDK 17 feature cycle: sealed classes were finalized after preview in JDK 15 and JDK 16; strong encapsulation of internals and macOS/AArch64 support landed as part of the same release train.
• After GA: update work moved to the jdk17u line, while the OpenJDK JDK Project continued six-month feature releases.

Related projects

• OpenJDK 17 sits between the JDK 11 and JDK 21 LTS generations. It is maintained through the JDK Updates effort, while experimental and longer-horizon work around Panama, Valhalla, Loom, Amber, and other OpenJDK projects feeds later feature releases.

ソース

• https://docs.oracle.com/en/java/javase/17/
• https://github.com/openjdk/jdk17u
• https://openjdk.org/jeps/409
• https://openjdk.org/projects/jdk/
• https://openjdk.org/projects/jdk/17/