[jira] [Closed] (SUREFIRE-1868) writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting

["Michael Osipov (Jira)" <ji...@apache.org>]

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

Michael Osipov closed SUREFIRE-1868.
------------------------------------
    Resolution: Invalid

It happens indeed, but for a reason and is caused by SUREFIRE-1788. The output comes from *your* code: https://github.com/apache/tika/blob/b6a1112909348db296c513b5efcbc2eeec835c80/tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/parser/mock/MockParserTest.java#L53-L74. 3.0.0-M5 started to handle this correctly, before that it was simply swallowed/ignored.

> writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting
> -------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1868
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1868
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 3.0.0-M5, 3.2.5
>         Environment: W10, oracle jdk8.0_202, mvn 3.6.3
>            Reporter: Tilman Hausherr
>            Priority: Minor
>
> I'm getting this text at the end of the tests
> "Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.apache.tika.utils.ServiceLoaderUtilsTest
> writing to System.outwriting to System.errwriting to System.outwriting to System.errwriting to System.outwriting to System.errwriting to System.outwriting to System.errwriting to System.outwriting to System.err"
> How to reproduce:
> - get the Apache Tika project ("main" branch) from https://github.com/apache/tika/
> - change "3.0.0-M4" to "3.0.0-M5" in the pom.xml of the parent subproject
> - build
> - it happens with the first subproject (tika-core)
> The build doesn't stop, but in my IDE it appears in red so it's probably a warning or an error.
> It does not happen with 3.0.0-M4.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)