Add Mockito Java agent surefire config in reactor modules

[timtebeek]

• Fixes AddMockitoJavaAgentToMavenSurefirePlugin inserts odd empty argLine and configures dependency-plugin for no apparent reason? #1168

Problem

In a multi-module (reactor) build where the parent pom manages maven-surefire-plugin and maven-dependency-plugin in <pluginManagement> but does not declare them in <build><plugins>, running AddMockitoJavaAgentToMavenSurefirePlugin on a child module produced a pointless partial change:

• an empty <argLine></argLine> property was added,
• the maven-dependency-plugin (with the properties goal) was added,
• but the maven-surefire-plugin with the actual -javaagent:... argLine was never added.

This is exactly what the reporter saw: an "odd empty argLine and dependency-plugin for no apparent reason", with nothing that actually wires up the Mockito agent.

Root cause

AddPluginVisitor.isAcceptable bails out when filePattern == null and the module's parent pom is part of the same reactor:

if (mrr == null || mrr.parentPomIsProjectPom()) {
    return false;
}

The surefire AddPlugin was invoked with filePattern == null, so it was silently skipped on reactor child modules. The dependency-plugin AddPlugin, however, is invoked with a **/pom.xml filePattern, which bypasses that guard — hence the inconsistent, half-applied result.

Fix

Pass the same **/pom.xml filePattern for the surefire AddPlugin so the configuration is applied consistently. The child module now gets a complete, working setup: the @{argLine} property, the dependency-plugin properties goal, and the surefire plugin with the Java agent argLine that references them.

Added a test reproducing the reporter's structure (parent manages both plugins in pluginManagement, child only declares the Mockito test dependency).