This appears to be a bug in maven-failsafe-plugin v. 3.5.3. Upgrading to v 3.5.4 or downgrading to c 3.5.2 fixes the issue.
maven-failsafe-plugin