Unleash Client v10/11

[victornoel]

Hi,

Is there any plan to move to the latest Unleash Client for the Unleash integration?
I see there are breaking changes in v10 (cf https://github.com/Unleash/unleash-client-java/blob/main/v10_MIGRATION_GUIDE.md) though, so maybe you are keeping with v9 on purpose?

Would you be open to contributions maybe for doing that?

Thank you!

[aepfli]

@liran2000 @sighphyre i thinks this is a topic for you as you are the code owners.

In general we are always happy to get contributions, and if it is an upgrade to a more recent version, there is normally nothing that speaks against it. Happy to review and support here ;)

[jarebudev]

FYI one thing that I experienced when moving to v10 of unleash-client-java was that in v10, it depends on a native libgcc library - libgcc_s.so.1 so even though it's a Java client, the v10 versions of unleash-client-java are not currently portable.

This issue is still open Unleash/unleash-java-sdk#275

[victornoel]

@jarebudev ha! that explains it, thanks, I will try to raise the subject there and see what's up nowadays :)

[victornoel]

A quick look at the doc of latest version of Yggdrasil (the thing that was causing issues) seems to highlight the fact that i's not requiring (anymore?) any native libs, it says it runs purely in the JVM using WASM: https://github.com/Unleash/yggdrasil/tree/main/java-engine

This is a good sign! I will try to see how easy it is to migrate to it then :)

[victornoel]

Looks like it's easy except for tests because the schema of the features.json seems to have changed, I will create a PR soon and we can discuss there how best to deal with this :)

[victornoel]

It is here: #1552

@liran2000 (and @sighphyre ideally), could you take a look when you have time? No urgency from my side of course :)