You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jörg Hohwiller (JIRA)" <ji...@apache.org> on 2019/05/03 16:21:00 UTC
[jira] [Created] (SUREFIRE-1665) JUnits fail with Java11:
IllegalArgumentException: Stream stdin corrupted. Expected comma after
third character in command 'FATAL ERROR in native method: processing of
-javaagent failed'
Jörg Hohwiller created SUREFIRE-1665:
----------------------------------------
Summary: JUnits fail with Java11: IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command 'FATAL ERROR in native method: processing of -javaagent failed'
Key: SUREFIRE-1665
URL: https://issues.apache.org/jira/browse/SUREFIRE-1665
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support
Affects Versions: 3.0.0-M2, 2.20.1
Reporter: Jörg Hohwiller
Attachments: 2019-05-03T18-10-11_458-jvmRun1.dumpstream, 2019-05-03T18-10-11_458.dumpstream
As discussed in SUREFIRE-1601 I create a new issue.
I want to make my project (java,maven,junit,surefire) to work with Java11. However, surefire fails to execute the tests when run with Java11 (works fine with Java 1.8).
```
IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command 'FATAL ERROR in native method: processing of -javaagent failed'
```
Attached are the surefire reports of the affected project (which is actually the test-case of a maven archetype). You can find the entire code here:
[https://github.com/hohwille/devon4j/tree/feature/java-11-surefire]
(When cloning please ensure you checkout the branch {{java-11-surefire}}).
The github pull-request for it can be found here:
[https://github.com/devonfw/devon4j/pull/84]
As you can see we are using travis-ci and JDK 1.8 build is green while JDK 11 build fails:
[https://travis-ci.org/devonfw/devon4j/builds/527844661?utm_source=github_status&utm_medium=notification]
I hope to have served with all the information required for you to trace down and fix the issue. In case you are still missing any information do not hesitate to ask.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)