Hi all,
We noticed that (due to
https://github.com/apache/maven-surefire/pull/702) `error`
and `failure` elements no longer contain the stack trace as their content
(without a `stackTrace` element). We think this is a regression that needs
to be addressed prior to releasing 3.2.4.
Please let me k
olve some use cases without using internal stuff, please
> ping us, so we can add support for that use case as well to new M4 API, as
> depending on internal/impl stuff of Maven just leads to inevitable
> breakage.
>
> Thanks
> T
>
> On Fri, Oct 7, 2022 at 9:52 PM Guillaume
ecific about the exact breaking changes ?
>
> Le mar. 4 oct. 2022 à 12:42, Marc Philipp a écrit :
>
> Hi everyone,
>
>
> We’re maintaining a Maven extension and testing it against the latest
>
> snapshots. After the merge of https://github.com/apache/maven/pull/703 our
>
?
Thanks,
Marc
--
Marc Philipp
Senior Principal Software Engineer
Gradle GmbH
Firmensitz: Danckelmannstr. 21, 14059 Berlin, Germany
Registergericht: Amtsgericht Charlottenburg, HRB 162310
Geschäftsführer: Dr. Rolf Dockter
P. +49 30 609886880
W. gradle.com
[image:
https://dpesummit.com
ind these invocations together, but the engine
> will be run over and over again. JUnit does support streaming tests in a
> lazy way via the DynamicTest API. It would be great if this could somehow
> be exposed via the LauncherDiscoveryRequest. That would IMHO really solve
> this issue.
&
Hi Emond and Tibor,
I’m glad you discovered the new LauncherSession API which was added for this
purpose. The JUnit 5.8 GA release will come in the next few days.
As you mentrioned, the official documentation does not (yet!) do a good job of
explaining its intended use case:
https://junit.org/j
expect the changes would mostly have to be made in Jenkins.
Cheers,
Marc
[1] https://the-asf.slack.com/archives/C7Q9JB404/p1555263260044100
[2]
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/
Marc Philipp
Senior Software Engineer
Gradle
W. gradle.com
