Closed julianhyde closed 10 years ago
Are you using this in a project that sets the Maven property dep.guava.version
?
No, I'm not setting dep.guava.version
.
I'm specifying the guava version 11.0.2 explicitly in my pom.xml, but that shouldn't prevent tpch getting the version it needs.
I've re-tried and everything seems to have mysteriously started working correctly. Closing this pull request.
Guava is already set to 16.0.1 in the
dependencyManagement
section of the parent POM (airbase). Can you explain the motivation for this change?