> > As I am on x86 and I wanted to simulate what would happen to users on ARM, > I just did it other way around - I introduced the dependency with > classifier linux-aarch_64. > > … > Surprisingly, the installation step succeeded on x86 even the dependency > was for aarch. However, the startup check went to else branch (2) and I saw > that the provider was not Corretto provider but the default - SunJCE. So > that tells me that it basically falls back to the default which is what we > want. >
I raised concerns about this because we have no other dependencies that use the classifier in the pom file to bind us to a particular arch. The loading of the native code isn't my concern. I'm uneasy (without further investigation) with publishing cassandra pom files that classify us to " x86_64". For example, how the jar files differ between classifiers for this project. I'm also curious if there's a way to bundle the native files for all arch, like we do for other libraries, with runtime just loading what's correct.
