-
Notifications
You must be signed in to change notification settings - Fork 939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JLine 3.24.1 and JAnsi 2.4.0. #7419
Conversation
This PR is still waiting for an update on sbt/jline2. |
JLine 3.24 doesn't work on JDK 8 — better stop at 3.23 (reference: scala/scala-dev#856) (I think that's what Yoshida-san is trying to alert us to, above) |
JLine 3.24 contains the fix I need. I could ask the developer of JLine to backport it to 3.23.1, but I don't know how he will feel about it since no other such patch releases have been done in the past. I made the request: jline/jline3#888 Optionally we could create our own branch of JLine3 as we have done with JLine2, but at some point cleaning up the whole JLine dependency thing should be planned. I can help if there is a clear direction we are going to take. Does this imply that scala will try to support JDK8 for ever? |
Unclear. So far, keeping support hasn't been painful. Perhaps at some point we'll decide a tipping point has been reached for the costs of continuing support have become too high. Anyway, it's a moot point for now, as I see that the JLine 3 maintainer just said that they will restore JDK 8 support in 3.24.1. So let's wait for that. |
f12c074
to
1f3b982
Compare
Updated the PR with JLine 3.24.1 (was 3.24.0) |
@eed3si9n did you get a chance to release sbt/jline2 already? If you could tell the version number, I can update it to this PR. |
1f3b982
to
c07ee84
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
When I take current 1.10.x, run
|
macOS 14.2, |
I can reproduce the problem. The fix is to bump the version number to |
Thanks Eugene, that fixes it 👍 |
Fix #7371