Revert JLine to version 3.29.0 for Scala 2.13.17#11135
Merged
SethTisue merged 1 commit intoscala:2.13.xfrom Sep 23, 2025
Merged
Revert JLine to version 3.29.0 for Scala 2.13.17#11135SethTisue merged 1 commit intoscala:2.13.xfrom
SethTisue merged 1 commit intoscala:2.13.xfrom
Conversation
When running the REPL through `sbt console`, the JLine jar from both the compiler and sbt seem to be on the classpath. It looks like classes may be loaded from either jar, depending on the time the class is needed. We need to figure out how to isolate this better. For 2.13.17 it seems apropriate to keep JLine at 3.29. Compared to past activity, there seem to be more substantial changes in the 3.30 version.
SethTisue
approved these changes
Sep 23, 2025
SethTisue
added
the
internal
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
3 participants
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.
When running the REPL through
sbt console, the JLine jar from both the compiler and sbt seem to be on the classpath. It looks like classes may be loaded from either jar, depending on the time the class is needed.We need to figure out how to isolate this better. For 2.13.17 it seems apropriate to keep JLine at 3.29. Compared to past activity, there seem to be more substantial changes in the 3.30 version.
sbt/sbt#8294