[
https://issues.apache.org/jira/browse/PHOENIX-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182580#comment-17182580
]
Istvan Toth commented on PHOENIX-6094:
--------------------------------------
You are breaking new ground here, [~larsh].
The last time I worked on Java 11 compatibility was last year, an even then I
only ran the tests (not compiled) with Java 11, and it was well before the code
coverage stuff was added. The fact that you're running into this now suggests
that no-one else has run a full test suite (or bothered to file a Jira) with
Java 11 in the last few months, either.
I am pleasantly surprised that master even got as far as building, and starting
to run the tests with Java 11 :)
I see no harm in keeping up-to-date with the Jacoco plugin, and adding proper
support for JDK11 is long overdue.
I suggest updating to the latest and greatest Jacoco *0.8.5* instead of 0.8.4
in *both* *branches* while we are at it (unless that breaks something in 4.x of
course).
> Update jacoco plugin to 0.8.4 in Phoenix 5.x
> --------------------------------------------
>
> Key: PHOENIX-6094
> URL: https://issues.apache.org/jira/browse/PHOENIX-6094
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 5.1.0
>
> Attachments: 6094-master.txt
>
>
> {code}
> [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM
> 1. See FAQ web page and the dump file
> /home/lars/dev/phoenix/phoenix-core/target/surefire-reports/2020-08-22T09-00-56_131-jvmRun1.dumpstream
> {code}
> Causing all (local) test runs to fail.
> I found a recommendation here:
> https://stackoverflow.com/questions/55272870/surefire-maven-plugin-corrupted-stdout-by-directly-writing-to-native-stream-in
> Updating jacoco indeed fixed the problem.
> Note: I'm using Java 11.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
