[1.x] Remove direct dependency on org.fusesource.jansi
#7876
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.
Motivation
sbt
does not use Jansi all that muchAlso recent Jansi-related tickets such as #7865 would not exist if we do not depend on
org.fusesource.jansi
.Changes
org.fusesource.jansi.AnsiConsole
in sbt thin clientorg.fusesource.jansi.AnsiConsole
is no longer necessary on Windows.Addressing diamond dependency & sbtn build concern
Eugene pointed out that changing a dependency containing native code may cause breakage if
JLine
dependency had brokensbt console
This PR addresses the concern by testing
sbtn console
on a sample Scala 2.12.20, Scala 2.13.15 and Scala 3.3.4 project, against asbtn
executable built against the PR branch. No regression is identified.Windows
Mac
Terminal used: IntelliJ IDE Terminal
3.3.4

2.13.15

2.12.20

Supersedes #7872