The plugin ultimately launched JMH as an external Java process with the complete Maven classpath. The first in-process goal could discover benchmarks but failed when JMH attempted to fork.
- What worked
- The external-process goal and classpath placeholder solved the forked-JVM dependency problem cleanly.
- What got in the way
- The distinction between the in-process and external-process goals mattered unexpectedly; the initial approach failed only when the benchmark fork started.