Hello Enrico, Would you create an issue in Jira? I will fix it in the nearest release. (Let's continue our discussion in Jira.) Yes, it is minor issue however annoying because you see the dump file. Details: The only problem is the order of these two lines. First line writes to a native Std/Out and second line wraps the stream to surefire format:
*Filter filter = jUnit48Reflector.isJUnit48Available() ? createJUnit48Filter() : null;createRunListener( reporterFactory, consoleStream )* Cheers Tibor On Sun, Mar 4, 2018 at 9:14 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > Using the '-Dgroups' parameter I get this warning. > It seems not a showstopper but the fix may be simple. > Surefire itself is corrupting stdout while writing a WARNING. > It is related to my issue > https://issues.apache.org/jira/plugins/servlet/mobile#issue/SUREFIRE-1453 > > > Thoughts? > Enrico > > > # Created on 2018-03-04T08:36:54.490 > Corrupted STDOUT by directly writing to native stream in forked JVM 1. > Stream '[WARNING] Couldn't load group class 'MinimumAcceptance' in > Surefire|Failsafe plugin. The group class is ignored!'. > java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma > after third character in command '[WARNING] Couldn't load group class > 'MinimumAcceptance' in Surefire|Failsafe plugin. The group class is > ignored!'. > at > org.apache.maven.plugin.surefire.booterclient.output. > ForkClient$OperationalData.<init>(ForkClient.java:511) > at > org.apache.maven.plugin.surefire.booterclient.output. > ForkClient.processLine(ForkClient.java:209) > at > org.apache.maven.plugin.surefire.booterclient.output. > ForkClient.consumeLine(ForkClient.java:176) > at > org.apache.maven.plugin.surefire.booterclient.output. > ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88) > at java.base/java.lang.Thread.run(Thread.java:844) > Il sab 3 mar 2018, 13:34 Tibor Digana <tibordig...@apache.org> ha scritto: > > > Maybe disappointed a bit on how we run the build with Java 1.8 and > another > > J7 - J10 used in all Tests (unit + integration tests). > > $ mvn install -P run-its -nsu -Dintegration-test-port=8000 > > -Dintegration-test-stop-port=8001 "-Djdk.home=d:\Program > Files\Java\jdk10" > > -Djacoco.skip=true > > There were several reasons. > > Maven plugins failed with J9, JUnit 5 Provider in future Surefire > requires > > J8, and the last is the JavaDoc check which runs within JavaC and it > forced > > the contributors to write JavaDoc correctly in the beginning of > > development. > > > > T > > > > On Sat, Mar 3, 2018 at 12:48 PM, Tibor Digana <tibordig...@apache.org> > > wrote: > > > > > Typo, the version is 2.21.0 of course. > > > > > > On Sat, Mar 3, 2018 at 12:42 PM, Tibor Digana <tibordig...@apache.org> > > > wrote: > > > > > >> Hi, > > >> > > >> We solved 33 issues: > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > > >> ctId=12317927&version=12341630 > > >> > > >> There are still a couple of issues left in JIRA: > > >> https://issues.apache.org/jira/i#issues/?jql=project+%3D+ > > >> SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC > > >> > > >> Staging repo: > > >> https://repository.apache.org/content/repositories/maven-1402/ > > >> https://repository.apache.org/content/repositories/maven-140 > > >> 2/org/apache/maven/surefire/surefire/2.21.0/surefire-2.21. > > >> 0-source-release.zip > > >> > > >> Source release checksum(s): > > >> surefire-2.21.0-source-release.zip sha1: > 6927024eefa0b8c80dee70efa014f1 > > >> f421d7844b > > >> > > >> Staging site: > > >> http://maven.apache.org/surefire-archives/surefire-LATEST/ > > >> > > >> Guide to testing staged releases: > > >> http://maven.apache.org/guides/development/guide- > testing-releases.html > > >> > > >> Vote open for 72 hours. > > >> > > >> [ ] +1 > > >> [ ] +0 > > >> [ ] -1 > > >> > > >> Cheers > > >> Tibor > > >> > > > > > > > > > -- > > > -- Enrico Olivelli >
