gh-116 Correctly compile and fix Hazelcast2CacheMetrics

[kerkhofsd]

Fixes #116

[thijslemmens]

@kerkhofsd Shouldn't we add caching metrics to the smoke tests?

[driesdeproost]

build fails though

[kerkhofsd]

@thijslemmens problem is that this problem doesn't show in current integration testing setup,

It requires a clustered Alfresco environment (including a valid license)...

[thijslemmens]

and a clustered setup is hard because of bootstrapping. Op vr 9 jul. 2021 om 16:31 schreef Daan Kerkhofs ***@***.***>:

…

@thijslemmens <https://github.com/thijslemmens> problem is that this problem doesn't show in current integration testing setup, It requires a clustered Alfresco environment (including a valid license)... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#119 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSIMZQGDPTK3SG7CV4SKPTTW4B3XANCNFSM5AC34MJA> .

[kerkhofsd]

To avoid the need of reflection in Hazelcast2CacheMetrics, we now compile against and build with an older, fixed Hazelcast version (2.4).
In new Alfresco versions, the OOTBox HazelcastCacheMetrics, included in Micrometer, is used anyway.

Added some minimal tests for the Hazelcast2CacheMetrics class.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

90.9% Coverage
0.0% Duplication