Railway Deployment #e584f8 fix: pin JDK 21 via NIXPACKS_JDK_VERSION - #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Nixpacks build failed during the Maven compile phase with "release version 21 not supported" because the jdk21 nixPkgs entry did not reliably activate JDK 21 as the active javac on PATH.
Solution
Set NIXPACKS_JDK_VERSION = "21" in nixpacks.toml so Nixpacks provisions and activates JDK 21 for all build phases, keeping maven in the setup packages so the Maven compile step succeeds.
Changes
nixpacks.tomlContext
48b6052Generated by Railway