Native Maven tests failed when reactor modules had no packaged jar (e.g., POM-only or source-less modules), causing “Missing jar-file …” or null artifact errors.

• Dependency resolution

  • Accept reactor output/test-output directories as classpath entries when packaged files are absent.
  • Skip metadata exclusion wiring when no artifact file exists to avoid NPEs.
  • Guard JUnit dependency inference against unresolved artifacts.

• Repro and coverage

  • Added reproducer project with a source-less module and a consuming test module.
  • Added functional test to assert native tests proceed without missing-jar failures.

Example adjustment:

Optional<Path> reactorOutput = resolveClassesDirectoryFromReactor(artifact);
if (reactorOutput.isPresent()) {
    Path output = reactorOutput.get();
    if (Files.exists(output)) {
        logger.debug("ImageClasspath Entry: " + artifact + " (" + output.toUri() + ")");
        return output; // use reactor output when no jar exists
    }
}

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.