Closed pveentjer closed 8 months ago
The job Simulator-pr-builder
of your PR failed. (Hazelcast internal details: build log, artifacts).
Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.
---------ERRORS----------- -------------------------- [ERROR] Failed to execute goal on project driver-hazelcast4plus: Could not resolve dependencies for project com.hazelcast.simulator:driver-hazelcast4plus:jar:2.0-SNAPSHOT: Failed to collect dependencies at com.hazelcast:hazelcast:jar:5.4.0-SNAPSHOT: Failed to read artifact descriptor for com.hazelcast:hazelcast:jar:5.4.0-SNAPSHOT: The following artifacts could not be resolved: com.hazelcast:hazelcast:pom:5.4.0-SNAPSHOT (absent): Could not transfer artifact com.hazelcast:hazelcast:pom:5.4.0-SNAPSHOT from/to backup-repo (https://repo2.maven.org/maven2/): repo2.maven.org: Unknown host repo2.maven.org -> [Help 1] -------------------------- [ERROR] -------------------------- [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. -------------------------- [ERROR] Re-run Maven using the -X switch to enable full debug logging. -------------------------- [ERROR] -------------------------- [ERROR] For more information about the errors and possible solutions, please read the following articles: -------------------------- [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException -------------------------- [ERROR] -------------------------- [ERROR] After correcting the problems, you can resume the build with the command -------------------------- [ERROR] mvn-rf :driver-hazelcast4plus --------------------------
The old architecture was designed for Java based servers and clients and 'optimized' for Hazelcast.
With the new architecture, there is a lot more flexible and Simulator architecture is a lot less Hazelcast specific. Which makes it a lot easier to test non Java based products.
It also opens the door for Hazelcast non Java client testing.