https://bz.apache.org/bugzilla/show_bug.cgi?id=68460
Jaikiran Pai <jaiki...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
OS| |All
Target Milestone|--- |1.10.15
Resolution|--- |FIXED
--- Comment #2 from Jaikiran Pai <jaiki...@apache.org> ---
This is a genuine issue. Thank you for raising this - I'm surprised no one else
ran into this thus far against recent Java versions.
Hello Thomas, I see you provided a patch for this issue. Thank you for that. I,
however, took slightly different approach and remove the registration of the
Provider (the call to Security.addProvider()) from that code path because the
Java SE SSLContext notes that TLS will be available at runtime. So we don't
have to find a Provider for TLS and then add it back using
Security.addProvider().
I've pushed a change to Ant upstream which should be available in next release
(no specific date yet). In the meantime, this change should be available for
testing in Ant's nightly build
https://ci-builds.apache.org/job/Ant/job/Ant_Nightly/lastCompletedBuild/artifact/.
Build 204 and later should have this change.
--
You are receiving this mail because:
You are the assignee for the bug.
