https://issues.apache.org/jira/browse/CRYPTO-136 asks that the
https://wiki.openssl.org/index.php/FIPS_mode_set() and FIPS_selftest()
functions be exposed in commons-crypto. (There is also
https://wiki.openssl.org/index.php/FIPS_mode(), which we'd want to
include.)
When exposed in OpenSSL, we'll w
I'd very much prefer 11, unless 17 is necessary. I have a library that
currently depends on FileUpload 1.5, and only requires Java 8. For various
reasons, I've been very conservative with the required Java version. I was
already planning to make the jump to Java 11, so if FileUpload 2.0.0 moves
Hello!
I currently maintain the HTTP server library (Ring) for the Clojure programming
language, which is a functional lisp for the JVM. In order to parse multipart
requests, I lean on FileUpload. In the past that's been somewhat problematic,
as 1.x had a hard dependency on Java servlets, so I
Hi James,
Thank you for your email. I think this should be two PRs against git
master, with unit tests of course ;-)
HTH,
Gary
On Mon, Aug 14, 2023, 12:50 PM James Reeves wrote:
> Hello!
>
> I currently maintain the HTTP server library (Ring) for the Clojure
> programming language, which is a
For now git master is on Java 11. I plan on releasing 2.0.0-M2 within a
couple of weeks.
Gary
On Mon, Aug 14, 2023, 12:15 PM James Reeves wrote:
> I'd very much prefer 11, unless 17 is necessary. I have a library that
> currently depends on FileUpload 1.5, and only requires Java 8. For various
Libraries should be kept on the oldest safe (LTS) version forever, IMHO, to
avoid stranding legacy services.
On Mon, Aug 14, 2023, 9:15 AM James Reeves wrote:
> I'd very much prefer 11, unless 17 is necessary. I have a library that
> currently depends on FileUpload 1.5, and only requires Java 8.
Based on my experience, once an app is at legacy status in an enterprise,
your are not allowed to touch it and even less update its dependencies
(except for critical security updates). A new major version of a library is
out of scope anyway and especially in this case since it requires source
updat
Good point. But then why stop at 11? Spring ripped the bandage off in their
latest by requiring 17.
On Mon, Aug 14, 2023, 1:36 PM Gary Gregory wrote:
> Based on my experience, once an app is at legacy status in an enterprise,
> your are not allowed to touch it and even less update its dependenci
