[
https://issues.apache.org/jira/browse/MNG-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MNG-6382.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.5.4-candidate)
3.5.4
https://gitbox.apache.org/repos/asf?p=maven.git&a=commit&h=3c3a5901f35783289d502b67bfc520b8e6936ed8
> JANSI fails frequently with NumberFormatException when building in parallel
> ---------------------------------------------------------------------------
>
> Key: MNG-6382
> URL: https://issues.apache.org/jira/browse/MNG-6382
> Project: Maven
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.5.3
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: C:\Develop\_tools\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Develop\_tools\jdk-10.0.0
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> Reporter: Falko Modler
> Assignee: Hervé Boutemy
> Priority: Major
> Fix For: 3.5.4
>
>
> After upgrading from 3.3.9 to 3.5.4 my parallel Maven build fail frequently
> with:
> {noformat}
> java.lang.NumberFormatException: For input string: "34m"
> at
> java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.base/java.lang.Integer.parseInt(Integer.java:652)
> at java.base/java.lang.Integer.<init>(Integer.java:1096)
> at
> org.fusesource.jansi.AnsiPrintStream.filter(AnsiPrintStream.java:129)
> at
> org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:97)
> at
> org.fusesource.jansi.FilterPrintStream.write(FilterPrintStream.java:107)
> at
> org.fusesource.jansi.FilterPrintStream.print(FilterPrintStream.java:161)
> at
> org.slf4j.impl.MavenSimpleLogger.writeThrowable(MavenSimpleLogger.java:81)
> at org.slf4j.impl.SimpleLogger.write(SimpleLogger.java:319)
> at org.slf4j.impl.SimpleLogger.log(SimpleLogger.java:295)
> at org.slf4j.impl.SimpleLogger.error(SimpleLogger.java:593)
> at
> org.apache.maven.cli.CLIReportingUtils.showError(CLIReportingUtils.java:138)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:309)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> {noformat}
> This seems to have been [fixed in JANSI master
> branch|https://github.com/fusesource/jansi/commit/e45e4665538ba9234f5ee5d7b06d78d6a03deda3]
> but it has not yet been released. There is already a request for a bugfix
> release, see [issue 114 ("Need 1.17.1
> release")|https://github.com/fusesource/jansi/issues/114].
> Maven 3.5.4 should therefore upgrade to JANSI 1.17.1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
