Currently the profile foss-parent-verification is set to be activeByDefault (see pom).
However, when another profile is activated (e.g. foss-parent-run-its for running invoker tests because src/it exists), foss-parent-verification is not active anymore (see Maven's introduction-to-profiles). Another example would be during release, where the maven-release-plugin will set performRelease=true, this will inactivate foss-parent-verification as well.
Solution: Activate the profile, when src/main/java exists, the checks are useful only when there are sources anyway.
foss-parent-verificationis set to beactiveByDefault(see pom).foss-parent-run-itsfor running invoker tests becausesrc/itexists),foss-parent-verificationis not active anymore (see Maven's introduction-to-profiles). Another example would be during release, where themaven-release-pluginwill setperformRelease=true, this will inactivatefoss-parent-verificationas well.src/main/javaexists, the checks are useful only when there are sources anyway.