IIRC, that's how JaCoCo Maven Plugin [1] works as well: you have to
configure two executions. The first one sets up the Java agent, the
other one processes the collected data and writes a report.
That's not to say "this is the way", but people may already be used to
this kind of setup.
HTH,
This might be a better question for the dev list.
Thank you for your effort regardless. I would hate to see this become an
example of 'Maven is harder than Gradle'.
On Thu, Sep 23, 2021 at 3:55 AM Cédric Champeau
wrote:
> Hi folks,
>
> I'm the maintainer of the GraalVM native build tools plugin
They would need two executions yes, but they would not need to really know
about how surefire works with it. Native build tools plugin could in its
own docs explain that that execution is needed if junit tests are to be run
again, and the user would not have to touch the configurations of other
plu
Possibly, but as far as I understand it would just move the problem to a
different location, since the user would have to declare the 2d execution,
no? Something which is important is that I'm trying to avoid a breaking
change, that is to say that there are existing POM files which work today
that
Perhaps one way to make it so that users don't need to touch Surefire is to
have two executions for your plugin, the first one being in maybe
validation phase and doing
// inject the project
@Parameter(defaultValue = "${project}")
private org.apache.maven.project.MavenProject project;
...
project
Thanks, but I totally disagree with you. The evidence that it's an
implementation detail is that the previous version did NOT need any user to
configure anything: it just works and nobody complained that it was
"magic": it just did what it was supposed to do. The fact that I cannot
configure proper
> This means, in practice, that IF the native maven plugin is applied, THEN
> the surefire mojo needs to be configured to set this property. It's an
> implementation detail that users shouldn't have to worry about. For Gradle
> this was trivial to implement because we can just react to the presence
Hi folks,
I'm the maintainer of the GraalVM native build tools plugins for Maven and
Gradle. In the next release, we're moving to JUnit Platform 5.8, which now
integrates a "unique test id tracker", which before used to be implemented
in this plugin suite.
The goal of this ID tracker is to collec
