Hi All, The component name was indeed ill chosen for what is effectively an OpenSSL wrapper. Maybe we could make that obvious on the site by calling the page "Apache Commons Crypto, an OpenSSL wrapper".
I am in favor of adding more Java methods to wrap more OpenSSL APIs as PR #165 does, that seems like a natural fit. I do not see the need to convert this component into a multi-module Maven project. Keep it simple IMO. Gary https://github.com/apache/commons-crypto/pull/165 On Tue, Jun 14, 2022 at 9:10 AM Gilles Sadowski <gillese...@gmail.com> wrote: > > Hello. > > Contradicting comments about the latest contribution offer[1] suggest > that the scope of the [Crypto] component is ill-defined. > > Is it a Java wrapper around a specific library ("openssl")? > Is it a set of tools (a.o. strong random number generators) for developing > cryptographic applications in Java? > Is it both? Does it intend to be more? > > In order to simplify maintenance (and clarify expectations), shouldn't it > become a (maven) multi-module project, with explicit separation between > platform-agnostic functionality and platform-specific (native) codes? > > Regards, > Gilles > > [1] https://issues.apache.org/jira/browse/CRYPTO-162 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
