maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MNG-6372) On Windows Maven can output spurious ANSI escapes such as [0m [0m
Date Thu, 22 Mar 2018 07:03:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hervé Boutemy updated MNG-6372:
-------------------------------
    Description: 
Found during the release vote of Maven 3.5.3 on Windows spurious ANSI partial escape codes
such as [0m

A regression introduced by the upgrade of JAnsi to 1.17. Rumoured fixed in 1.18

notice: another issue from Jansi 1.17 exists, which is failure when run in parallel build
with NumberFormatException = see MNG-6382

  was:
Found during the release vote of Maven 3.5.3: 2 issues found on Windows only
1. spurious ANSI partial escape codes such as [0m = this issue
2. failure when run in parallel build with NumberFormatException = MNG-6382

A regression introduced by the upgrade of JAnsi to 1.17. Rumoured fixed in 1.18


> On Windows Maven can output spurious ANSI escapes such as [0m [0m
> -----------------------------------------------------------------
>
>                 Key: MNG-6372
>                 URL: https://issues.apache.org/jira/browse/MNG-6372
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.5.3
>            Reporter: Stephen Connolly
>            Priority: Major
>
> Found during the release vote of Maven 3.5.3 on Windows spurious ANSI partial escape
codes such as [0m
> A regression introduced by the upgrade of JAnsi to 1.17. Rumoured fixed in 1.18
> notice: another issue from Jansi 1.17 exists, which is failure when run in parallel build
with NumberFormatException = see MNG-6382



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message