https://bz.apache.org/bugzilla/show_bug.cgi?id=60394
Mark Thomas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Mark Thomas <[email protected]> --- This is going to become increasingly problematic given the long lifetime of a Tomcat release compared to the lifetime of public Java releases. The pace of change of what is considered a minimal acceptable TLS configuration is also likely to cause problems. Users building locally can use a newer JDK. If they want to build using an older JDK because that is the version they are using in production then the expectation is that they use a supported JDK which should include any necessary updates. Release managers can work-around this by downloading manually or specifying a specific mirror. If we start to see issues with the CI system then we can use the same options as the release managers. At this point, I don't think we should start switching mirrors because people want to build with unsupported software. If the problem becomes more significant, we can re-evaluate. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
