We build with Java 8. The general idea was NetBeans 10 == Java 10 but since Java is getting so speedy with releases, I believe we might stick with LTSes. So our next target would be Java 11 (although right now there is a blocker issue for NetBeans with 11.0.1 so we are waiting on JDK 11.0.2 or something like that).
About the HumbleBundle Java books, they might be too many: * $1 books: 2 are Spring and Web Services, 1 is RxJava (while interesting, we don't use it). The Java 9 cookbook might be too much, just use the concurrency stuff we have. 'Algorithms and Data Structures' *might* be interesting, but I don't believe you will be contribute that much algorithmic stuff. * $8+ books: 5 are Java EE and Sprint, 3 are generic (Java 9, Java 11 and Java for beginners). I assume the generic one might come in handy... The Java EE ones might give you an idea about the tech but they won't necessarily help you to build tooling (like NetBeans) for that technology. * $15+ books: 7 are Java EE and Spring, 1 is Machine Learning and 3 are generic (about Java 11 and Learning Java through an Android game). It might help you more to read about Ant (Maven too perhaps), see some articles about the NetBeans Platforms (there are some old books too) and if you want to do UI you might have to read about Swing (also old old books here, they don't make them anymore :-) ). --emi On Sat, Nov 3, 2018 at 6:19 AM Emilio - Rareitor <[email protected]> wrote: > > Hello > > First I apologize if this has been publicly discussed and posted elsewhere > (in one of these lists even) and I have missed it. Regarding building and > running releases of Netbeans post 8.X, is there some sort of standard for > which JDK (of those available at the time) should it be possible to do either > or both of these in for each new Netbeans version? In other words: is there > some rule or "best practice" when consolidating what Netbeans N (N >= 9.0) > will be, which JDKs it should, or must, be possible to build and run it in > before the actual official release? Further, should there be, and would it be > best to explicitly put that in the documentation for each release? > I ask, really late if I'm being honest, because it seems like a logical > extension of the settled debate about the new Netbeans release cycle and its > distancing from the JDK release cycle itself or Oracle's new 3 year LTS > model. I don't remember reading it anywhere after that topic was decided in > the dev mailing list (again, might have missed it). > > On a completely separate topic, currently there's a sale on HumbleBundle (the > book bundle, Java by Packt) that includes a bunch of seemingly useful tools > for learning and or getting up to speed on Java development. Would any of you > consider this a worthwhile investment for someone who has used the language, > and Netbeans, but not delved deep into it? I'd like to learn enough so that I > can actually contribute to the Netbeans project, among others, in the future, > instead of just ask random stuff on the mailing list. > > Thank you. > > Emilio G.C. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
