[
https://issues.apache.org/jira/browse/CASSANDRA-18624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745423#comment-17745423
]
Michael Semb Wever commented on CASSANDRA-18624:
------------------------------------------------
My concern is not about runtime loading, but about putting the x86 classifier
into our pom file. No other dependency of ours is doing that. This impacts
third-party (maven) projects that use our pom files. I'm also concern about
tests, if we have a dependency that works one way with x86 and another with arm.
The only differences between the two classified jar files are the files:
* com/amazon/corretto/crypto/provider/libamazonCorrettoCryptoProvider.so
* com/amazon/corretto/crypto/provider/libcrypto.so
Is there a way for us to
a) provide binaries with so files for both archs, ensuring the correct arch is
loaded,
b) ensure tests on both arch can test both accp enabled and disabled paths,
c) not have arch hardcoded, or arch-variable, pom files in maven central ?
> Make Corretto Crypto Provider the Default
> -----------------------------------------
>
> Key: CASSANDRA-18624
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18624
> Project: Cassandra
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Jordan West
> Assignee: Ayushi Singh
> Priority: Normal
> Attachments: image.png
>
> Time Spent: 10h 10m
> Remaining Estimate: 0h
>
> [Amazon Corretto Crypto Provider|
> https://github.com/corretto/amazon-corretto-crypto-provider] is an
> alternative provider of TLS and cryptographic functions that has significant
> performance benefits for Cassandra. It is Apache 2.0 licensed and has been
> deployed in several existing large fleets.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
