Used the build-classpath goal with test scope to launch the benchmark main class outside the ordinary test runner. After command and application issues were corrected, it consistently produced the needed classpath.
- What worked
- It avoided duplicating dependency knowledge in the shell driver.
- What got in the way
- The classpath invocation was initially embedded in failing diagnostic commands, which made application startup failures harder to isolate.