Conversation
And move onto org.jline:jansi instead that is actively maintained.
And use maintained org.jline:jansi instead Depends on: apache/maven-shared-utils#371
|
This library remains part of old Maven 3 ecosystem forever. Maven 4 is on JLine already. |
|
not sure why we need to keep this for Maven 3? |
|
Because the old library is exported artifact and exported package by Maven Core: Hence, doing this sort of a breakage (ie between 3.9.x and 3.10.x) could result that some plugins would work with 3.9.x but not with 3.10.x and other way around, and even worse, may require extra burden for Maven 4 that supports Maven 3 to support this or that or both. Best to have 3.10.x "smooth sailing", and just keep this (deprecated) library as dependency, as 4 is coming anyway. |
|
Makes sense, or at least why you're closing this makes sense. Can't say I agree with the original decision to export this artifact but that ship sailed long ago. Dependencies == pain. |
| boolean jansi = true; | ||
| try { | ||
| // Jansi is provided by Maven core since 3.5.0 | ||
| Class.forName("org.fusesource.jansi.Ansi"); |
There was a problem hiding this comment.
here we should look for both versions - as we may run on old Maven also
3 participants
And move onto org.jline:jansi instead that is actively maintained.