Recently I faced the same exception. After a bit researching I found that maven-compat plugin solves the problem:
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-compat</artifactId>
<version>3.0.5</version>
<scope>test</scope>
</dependency>