...
- plexus application use case
- idea:idea running generate-sources (defined by the mojo)
- assembly:assembly running package (defined by the project)
- clover running tests
- jcoverage, modifying class files
- reports running tests, etc
...
plexus:test-runtime is like making an assembly. It would be wired in as the "executePhase " for assembly:assembly (see
below), and in turn "package" would be the executePhase for this goal. , unless it were intended to be attached like an assembly is (though the assembly plugin is probably capable of doing that on its own)
idea:idea running generate-sources
...
The project used needs to be a clone that lasts the life of the executed lifecycle and the idea:idea goal, but
goes back to normal afterwards so the effects don't hit other goals.
assembly:assembly running package (defined by the project)
This can be covered by the addition of <executePhase/> to the goal configuration, ie:
...
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<executePhase>package</executePhase>
<configuration>
...
</configuration>
</plugin>
Here, this would override anything specified on the mojo using @executePhase, if applicable, but otherwise would
behave identically.
Clover use case
M1 plugin:
...