My pom.xml has a dependency to include HazelCast 3.8.4, but the war includes HazelCast 3.2.1 instead. Turns out BikeEmotion has a dependency on HazelCast Client 3.2.1, which is good, but HazeCast-Client in turn has a dependency on an earlier version of HazelCast, which is the 3.2.1 that I do not want.
Basically I need to be able to exclude a specific version to force it to get 3.8.4, but there does not seem to be a way to do that.
<dependency>
<groupId>com.bikeemotion</groupId>
<artifactId>quartz-hazelcast-jobstore</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>com.hazelcast</groupId>
<artifactId>hazelcast-all</artifactId>
<version>3.8.4</version>
<scope>provided</scope>
</dependency>
Relevant links:
Eclipse uses wrong maven dependency in launch configuration
Maven loads wrong version of dependency
https://github.com/hazelcast/hazelcast/blob/master/hazelcast-client/pom.xml