Hi,
I just wanted to share a work-around for a bug in Hazelcast 3.4.2 that was
preventing me from using Hazelcast EC2 discovery.
The problem is simple: com.hazelcast/hazelcast/3.4.2 is not importing all
required packages from com.hazelcast/hazelcast-cloud/3.4.2, where the discovery
implementation lives.
The solution was to amend apache-karaf-cellar-3.0.3-features.xml (grabbed from
Maven repos) and make it depend on hazelcast-all instead of hazelcast. Then I
installed it into
${SMX_HOME}/local-repo/org/apache/karaf/cellar/apache-karaf-cellar/3.0.3/
I hope this saves someone else's day.
Would it be a big deal to import hazelcast-all instead of hazelcast in the
upcoming versions?
Dario Cimafonte
