Thanks for volunteering, @Sandeep More <moresand...@gmail.com> ! Sounds like a plan.
I'm not sure that it is EOL'd but new development will need to go into the new line. We will need to support java 8 for security and maybe other bug fixes for a bit. On Thu, May 1, 2025 at 2:50 PM Sandeep Moré <moresand...@gmail.com> wrote: > I have been thinking about this and I would like to volunteer as a release > manager for the last Java 8 knox release :) > > Once we release this we can continue with the JDK 17 development effort > which might be significant, following are some of the things that come to > my mind that need to be considered: > > 1. Unit tests, especially Hadoop Unit tests are going to break, I am > anticipating that this will be a major work exploring what support hadoop > has for JDK 17. > 2. Build changes, currently our builds run on JDK 8 and JDK 11, we will > need to move away from them. > 3. Dependency upgrades, like hadoop, we have libraries such as Pac4J that > will need to be upgraded. This will have a significant impact and will > involve some extensive testing (unit testing and functional testing). > 4. Notifications: We need a way to let the community know that Java 8 > support has been EOLd, this means sending out email communication to the > committee mailing list (u...@knox.apache.org), updating docs, updating > knox website and wiki. > > Let me know if you have any questions or thoughts. > > Best, > Sandeep > > On Mon, Apr 7, 2025 at 4:14 PM Sandeep Moré <moresand...@gmail.com> wrote: > > > Thanks for starting this thread Phil! > > > > We did some work to support running Knox on Java JDK. I recall a few > > issues with compiling but those were mostly due to our intent of > supporting > > JDK 8. > > Moving away from JDK 8 would help us a lot especially regarding Pac4J and > > spring upgrades. > > > > I think we would need a major Knox version for JDK 17 given this would be > > a breaking change. > > > > About releasing multiple versions, although I do not like the idea but I > > think it would be nice/necessary if we release one last version with CVE > > fixes for folks to give them some runway to upgrade. > > > > Just my thoughts :) > > > > Best, > > Sandeep > > > > On Mon, Apr 7, 2025 at 3:59 PM Phil Zampino <pzamp...@apache.org> wrote: > > > >> With Java 8 and 11 EOL approaching, and the associated limitations we've > >> encountered wrt upgrading some dependencies, it seems about time to move > >> the Knox project to a more current Java version. I propose we begin > >> development compiling with Java 17, and drop support for Java 8/11. This > >> will not be trivial, but will require some significant changes to the > >> source. > >> > >> Would such a change constitute a major Knox version increment (e.g., > >> 3.0.0)? > >> > >> Should we release one more version (e.g., 2.1.1) based on Java 8/11? > >> > >> Interested in your thoughts, > >> Phil > >> > > >
