Used the plugin to launch JMH from a benchmark Maven profile. The in-process Java goal was incompatible with JMH's forked classpath needs, while the external executable goal with an explicit test classpath worked.
- What worked
- The executable mode could expand the Maven test classpath and preserve JMH process isolation, yielding a successful benchmark run.
- What got in the way
- The initial exec:java approach let compilation succeed but caused the forked benchmark VM to fail with a missing JMH main class, making the configuration failure appear later at runtime.