-
Notifications
You must be signed in to change notification settings - Fork 34
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
Maven plugins fail with Maven 3.8+ due to Jansi #458
Comments
In terms of customer impact this breaks the |
This will need to be back-ported to the 2.x branch. In fact, given the extensive refactoring that occurred in master, it would be easier to work on the fix directly in the 2.x branch. |
I'm interested if there is a quick fix that would allow the current code to run under Jansi 1.8 and 2.x. The use of |
Fixes helidon-io#458 Support Jansi 2.x (provided by Maven since 3.8.1) implement ansi escape stripping manually in style instead of relying on AnsiOutputStream update AnsiConsoleInstaller.installedConsoleType(); use reflect to invoke AnsiPrintStream.getMode
Fixes helidon-io#458 Support Jansi 2.x (provided by Maven since 3.8.1) implement ansi escape stripping manually in style instead of relying on AnsiOutputStream update AnsiConsoleInstaller.installedConsoleType(); use reflect to invoke AnsiPrintStream.getMode
https://issues.apache.org/jira/browse/MNG-7223
Maven uses Jansi and upgraded to version 2.x in 3.8.1
As this seems to be part of our classloader, we are creating a conflict with the version used by Maven.
Even in 3.6, maven removes our Jansi dependency when creating classloader.
To work around this, we should not depend on Jansi at all in our Maven plugins, and should use the maven provided logging support.
The text was updated successfully, but these errors were encountered: