Hi Greg, Thanks for the KIP! This is important when we move to the new jdk version.
Just a minor comment, could we make it much clearer in the compatibility section? Like in the 1st line, we can directly say, "this change is backward compatible", then explain if SecurityManager is unsupported, we'll fall back to newer implementation. Also, what does this line mean here? "Users upgrading to Java 17+ (in which SecurityManager was deprecated) already receive a warning message on startup." Maybe we can remove it or add more words at the end? Anyway, +1 (binding) from me. Thank you. Luke On Tue, Jul 9, 2024 at 2:26 AM Greg Harris <greg.har...@aiven.io.invalid> wrote: > Hi all, > > I'd like to call a vote on > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1006%3A+Remove+SecurityManager+Support > > > Voting for this KIP would signal our intention to remove SecurityManager > support in the future when the project's minimum supported version is Java > 21. > > Thanks, > Greg Harris >
