On Tue, Feb 9, 2021 at 7:54 PM Eric Bresie <ebre...@gmail.com> wrote:
> So from an initial plan perspective I would assume part of the "table or > work" would involve > I'd like to point out one thing: currently, the oldest JDK on which NetBeans runs is JDK 8, but that does not mean it does not run on newer JDKs. Quite the opposite - I use NetBeans on newer JDKs, and I think 12.2 is supposed to run on JDK 15, 11 and 8, at very least (but probably on every version between 8 and 15, inclusive). I'd say we add support for running on up-to-date JDKs as they are released, so we are tracking the changes, as we can. Dropping support for JDKs (like e.g. support for JDK 8) is a different matter - I guess I'd say that depends on when our users will be OK with that move. For completeness, the set of JDKs for which the users can develop applications is different, and hopefully broader - e.g. we should (I hope!) support developing JDK 7 applications. Jan > > 1. For Netbean codebase, for applicable Java version, updated to reflect > removed (and deprecated) APIs (see (1); the ticket may be a "starter > point" > (epic) with children or follow up items as applicable) > 1. Maybe running code analysis or Netbeans Migration tips may help as > well. > 2. Updated build files (project properties, javac.source/target and > related references). > 1. This could involve transitioning from ant to maven/gradle to help > in dependency management aspects. > 3. Update libraries (i.e. once migrated to new Java API level, > dependency libraries will likely need updating) > 4. Update documentation (i.e. plan migration status updates [TODO, > tickets/PRs, assignee, Implemented, etc.], readmes, compatibility matrix > [what version works with what java version[, etc.). > 5. Modularize Netbeans projects (there may be overlap with this proposal > (2) ) > 6. Netbean Plugin Migration to ensure any API changes that may impact NB > Plugins are addressed > > Eric Bresie > ebre...@gmail.com > > Reference: > > 1. NETBEANS-5349 Update Netbeans Codebase to Account for > deprecated/removed API in Java 11 > 2. > > https://cwiki.apache.org/confluence/display/NETBEANS/JDK+Modules+Support+in+NetBeans+Module+Syste > > > On Mon, Feb 8, 2021 at 11:59 AM Neil C Smith <neilcsm...@apache.org> > wrote: > > > On Fri, 5 Feb 2021 at 18:58, Matthias Bläsing <mblaes...@doppel-helix.eu > > > > wrote: > > > Translating to today, LTS versions can be considered mostly identical > > > to the old times java released. We currently run on 11 (current LTS) > > > and support 8, I think the Java 17 LTS jump might be good time to speak > > > again. > > > > If we decide to continue with our LTS (another discussion!) my > > assumption would be that we wouldn't review this until after our first > > LTS on JDK 17 - in which case perhaps 6 months past JDK 17 release? > > > > > I don't see a big issue here. At some point it was discussed and > > > someone, I think Jaroslav, said, that in the old time, NetBeans was > > > able to be run on JDK-1. > > > > If that's the discussion I'm thinking of, it started as discussion > > about dropping support for Java editing on JDK 8 (in order to drop > > nb-javac). That got conflated with discussion about minimum JDK for > > the whole project and platform. I still think those two concerns > > should be considered separately. > > > > Best wishes, > > > > Neil > > > > --------------------------------------------------------------------- > > 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 > > > > > > > > >
