Hi all, Could a consensus solution be that for all JDK 8 - compatibility related items, any/all work related to that, we assign those issues to Svata -- and we try this for one release and see how that goes? If it fails, then in the release after that, we should all then have consensus to move away from JDK 8.
This does not solve the question of when we'll stop supporting a particular JDK release -- except that it sounds like "forever, as long as someone turns up to continue to support that release and in fact does so". Gj On Mon, Apr 10, 2023 at 8:32 PM Michael Bien <mbie...@gmail.com> wrote: > > On 10.04.23 06:20, Michael Bien wrote: > > > > Don't let maven distract us here, I only kept mentioning it since that > > was the area I have been working on. The whole java ecosystem moves > > on: Jetty, Jakarta EE, Spring, Jenkins, Maven, Lucene, (...) > > Since I just read the news in my RSS reader: > > ecj, the eclipse compiler did also move from JDK 11 to JDK 17 a few > weeks ago. > > recommended reading (linked comment and PR itself): > > https://github.com/eclipse-jdt/eclipse.jdt.core/issues/886#issuecomment-1479528341 > > best regards, > > -mbien > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
