Hi Robert,
I tested this change locally and yes it works fine with additional space
after -D
Here is note in Jira:
For now, leave GnuParser. Despite the upgrade advice in the GnuParser Javadoc
> ("since 1.3, use the DefaultParser instead"), it behaves differently (see this
> Stack Overflow answer
You cannot expose the interface
org.apache.maven.surefire.report.RunListener outside.
The users implement native Listener of JUnit5 and use it on the classpath
very close to the runner (JUnit4 or JUnit5) and their tests.
So it must be the *org.junit.platform.launcher.TestExecutionListener*.
Surefi
Hello,
Am Do., 16. Mai 2019 um 12:36 Uhr schrieb Tibor Digana <
tibordig...@apache.org>:
> Is it what Marc Philipp was asking me on the chat?
> The purpose looked like a top secret ;-) but it was not because Mark needed
> it for testing of some internal report.
> Now it looks like Junit5 wants to
Is it what Marc Philipp was asking me on the chat?
The purpose looked like a top secret ;-) but it was not because Mark needed
it for testing of some internal report.
Now it looks like Junit5 wants to remove the Surefire report out been dead
and move these features into Junit5.
The RunListener cou
Hello,
I'm currently working on a Maven extension that needs to be notified of
what happened during test execution in Surefire. Currently it is only
possible to register test framework specific listeners via the
setting [1]. However there is also the org.apache.maven.surefire.report.
RunListener
+1 (non-binding) - nice to see this under vote!
- Eric Lilja
On Wed, May 15, 2019 at 9:58 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12336941
>
> There are still a couple of issues left in JI
