On 2017-11-22 11:45, Colm O hEigeartaigh <[email protected]> wrote: > I can't reproduce the test failures in Kafka, HBase or Hive. However, I can > reproduce the build errors in security-admin. It's caused by this bug in > Maven: > > https://issues.apache.org/jira/browse/MNG-6298 > > The solution is to use Apache Maven 3.5.0 instead of 3.5.2.
Thanks, that helps... I'll get all three environments on 3.5.0 and then retry (after a pull) I imagine this kind of error is rare, but wonder if it would be worth using the maven-enforcer-plugin to validate that at least the mvn version (and anything else we want to check) is a 'sane' version (for us). See https://issues.apache.org/jira/browse/ATLAS-2245?filter=-2. We could check only min 3.5.0, or I guess exclude 3.5.2 with a error OR WARNING if we wanted, could be clearer? I'm happy to propose a patch if this is felt to be useful (once I'm over my build issues!)
