Skip to content

mise: move Java from Oracle JDK 26 to mise Temurin 25 LTS - #5

Merged
kosora623 merged 3 commits into
mainfrom
mise-java
Nov 13, 2026
Merged

kosora623 merged 3 commits into
mainfrom
mise-java

Conversation

@kosora623

Copy link
Copy Markdown
Owner

Oracle JDK 26 をやめて、mise の Temurin 25 LTS にする(java = "25"。mise の shorthand の vendor は temurin)。JDK 26 は LTS ではなく更新が止まっていて、授業の新しい課題は release 25。

  • mvnw.cmd は JAVA_HOME が無いと止まるので、User の JAVA_HOME を %LOCALAPPDATA%\mise\installs\java\25(mise が作るメジャー番号のジャンクション)に向ける。パッチを上げても変更は要らない
  • install.ps1: mise install の後に、mise current java のメジャー番号から JAVA_HOME を設定する
  • packages/winget.txt から Oracle.JDK.26 を消す。アンインストールで javapath も Machine PATH から消えた
  • 確認: mvnw の 3 種類(wrapper 3.3.4 / 3.3.2 only-script / 古いもの)すべてで mvnw -v が mise の JDK 25、release 25 のプロジェクトで mvnw test 20 件成功
  • 詳細と戻し方は notes/mise-migration.md

#4 の上に積んでいるので、#4 を先にマージしてください(README と install.ps1 の同じ場所を触っているため)。

A mise shim adds about 90 ms to every call. Node is now reached through
%LOCALAPPDATA%\mise\installs\node\lts, the junction mise keeps pointing
at the installed LTS, placed before the shims on the user PATH
(node -v 116 -> 28 ms, npm run 432 -> 317 ms). Go and Python still go
through the shims.

This gives up per-folder Node versions (.node-version / .nvmrc); no
project pins one today. Removing the entry from PATH falls back to the
shims.

install.ps1 sets the same order, and README / the profile comment
describe it.
java = "25" in the mise config installs Temurin 25 (the shorthand vendor
is temurin). JDK 26 is not an LTS and no longer gets updates, and the
newest class projects target release 25.

mvnw.cmd refuses to run without JAVA_HOME, so the user JAVA_HOME points
at %LOCALAPPDATA%\mise\installs\java\25, the major-version junction mise
keeps, and patch upgrades need no change. install.ps1 sets it after
mise install, taking the major version from `mise current java`.

Oracle.JDK.26 is dropped from packages/winget.txt; uninstalling it also
removed javapath from the machine PATH. The notes record the checks
(all three mvnw wrapper versions, mvnw test on a release 25 project) and
how to roll back.
The same binary copied as pyx.exe starts in about 10 ms every time,
while python.exe takes about 65 ms and stalls for 1 s on every other
launch, before any output. No foreign DLLs are loaded and there is no
IFEO or AppCompat entry for python.exe, so something is likely watching
process starts by name. Next steps need a ProcMon / WPR trace.
@kosora623
kosora623 merged commit 9eb2ed1 into main Nov 13, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant