The issue seems to be related to the older version of maven you are using, as you can see from our docs we advise Maven 3.2.5+ as a prerequisite for the scanner for maven.
With the latest release of the scanner we had to bump the version of a transitive dependency which is not supported by the version of Maven you are using.
Bumping Maven to 3.2.5 will fix the issue.