Re: JigSaw-ing NetBeans?
On Sun, Jul 22, 2018 at 7:18 PM Emilian Bold wrote: > In the 1st idea if everything is static you don't need lookup listeners > perhaps, you don't need module.install, etc. Probably doesn't gain you much > except realise NetBeans would work without our specific module system. Create a maven project that depends on every NetBeans module. Then use my maven-merge-dependencies maven plugin (on Github, part of Giulius) to try it ( unlike the assembly plugin, it will concatenate META-INF/services files and merge properties files under META-INF). Probably the result would violate lots of assumptions, but with some work I recall from performance work over a decade ago that the biggest win was putting everything on the boot class path. Any such jar will do better if the classes are ordered in load-order. -Tim > > The 2nd ides is about compiling at runtime. If an user never touches a > feature it remains source code on disk. The stuff that gets used gets > compiled at first module load by the module system. Many modules are simple > and just need javac and the dependencies JARs in the classpath, it might > work. Also not a big feature but it might make things interesting. What if > fixing a small bug is just applying a .patch to the IDEs own source code > which will get recompiled on restart? Odd, right? > > --emi > > ‐‐‐ Original Message ‐‐‐ > > On 21 July 2018 10:59 AM, Geertjan Wielenga > wrote: > > > Cool thought experiments. It would be interesting to explore -- although > I > > > > wonder how much real performance gains there'd be with the first > approach, > > > > i.e., one of the best features of NetBeans is its modularity, if we were > to > > > > explore dropping that, or creating some kind of distribution without > that, > > > > would we gain anything -- and if that would be performance, would that be > > > > significant enough to warrant all the work involved? The second approach > is > > > > basically what we have right now in Apache NetBeans Git, i.e., the > 9.0-vc3 > > > > tag can be cloned by anyone and then built from scratch. > > > > Gj > > > > On Sat, Jul 21, 2018 at 9:10 AM, Emilian Bold < > > > > emilian.b...@protonmail.ch.invalid> wrote: > > > > > I've been wondering the other way: what if we rip out all the module > > > > > > system and have a single fat JAR for NetBeans? How much can we > optimise if > > > > > > we know there will be no runtime module enable/disable, no layer > changes, > > > > > > no global services showing up, etc? > > > > > > How many plugins do users really install? What if they generally > install 0 > > > > > > modules? > > > > > > On the other side of the spectrum: could we perhaps distribute most > > > > > > modules are source code and compile on the fly? What if we have a small > > > > > > binary bootstrap and the obvious dependency on javac and just make the > > > > > > whole release a big source tar? Would certainly make 'convenience > binaries' > > > > > > a thing of the past. > > > > > > --emi > > > > > > ‐‐‐ Original Message ‐‐‐ > > > > > > On 14 July 2018 2:35 AM, Laszlo Kishalmi laszlo.kisha...@gmail.com > > > > > > wrote: > > > > > > > Well this question is to Jaroslav Tulach mostly. > > > > > > > > From Java 9 there are three modularization system in Java. OSGI, > > > > > > > > NetBeans and Java's JigSaw. > > > > > > > > My question is could NetBeans be ported on JigSaw? What would we gain > > > > > > > > form that movement (if any), and what would be the pain points. > > > > > > > > I'd even would like to see a deep analysis on this topic on Jarda's > blog. > > > > > > > > Thank you in advance! > > > > > > > > Laszlo Kishalmi > > > > > > > To unsubscribe, e-mail: > dev-unsubscr...@netbeans.incubator.apache.org > > > > > > > > For additional commands, e-mail: > dev-h...@netbeans.incubator.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.incubator.apache.org > > > > > > For additional commands, e-mail: > dev-h...@netbeans.incubator.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.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > -- http://timboudreau.com
[RESULT][VOTE] Release Apache NetBeans 9.0 (incubating) [vote candidate 3]
Hi all, After being opened for much more than 72 hours, the vote for releasing incubating-netbeans-java-9.0 [vc3] passed with 13 PPMC +1 votes, 16 non-PPMC +1s (from others on the Apache NetBeans mailing list), no 0 and no PPMC -1 votes. . Note that at this point only the IPMC votes are binding. So I am differentiating between PPMC votes (which will be binding, after we graduate) and non-PPMC votes. Also, remember to add "(binding)" to your PPMC votes. The link to the vote thread is https://lists.apache.org/thread.html/a644bb8e3ba2cbd06328bb004f1b18b4171763cd3d78a9131615f687@%3Cdev.netbeans.apache.org%3E PPMC +1 votes: Geertjan Wielenga Junichi Yamamoto John Kostaras Antonio Vieiro Laszlo Kishalmi David Heffelfinger Reema Taneja Neil C Smith John McDonnell Tushar Joshi Bertrand Delacretaz Ate Douma Josh Juneau Non-PPMC +1 votes: Nelson Cazonda Ludovic Hochet Mario Schroeder Glenn Holmer chegekinuthia Kai Uwe Pel Gaurav Gupta Thilina Ranathunga Yaroslav Ilchenko Arunava Sinha Vikas Prabhakar Mike Billman tmsanchez pblakez Oliver Rettig ldeseta Thanks to all who examined the release artifacts and voted. After the Community Acceptance results, I will start a new thread for the IPMC vote. Thanks all, Emilian Bold on behalf of the Apache NetBeans PPMC - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: What will happen to NB 8.x (and earlier)?
I'm just not used at the glacial speed corporations move. Must be nice getting a pay-check while waiting for planetary alignments and such :-) --emi ‐‐‐ Original Message ‐‐‐ On 21 July 2018 10:37 AM, Geertjan Wielenga wrote: > On Sat, Jul 21, 2018 at 8:25 AM, Emilian Bold < > > emilian.b...@protonmail.ch.invalid> wrote: > > > Long ago I wanted to start a 'NetBeans Archival' project but nobody was > > > > interested in joining. I guess it's inevitable that some historical data > > > > will be lost. > > > > The full hg history is mirrored here https://github.com/ > > > > emilianbold/netbeans-releases > > > > I also have some older repositories here https://bitbucket.org/netbeans/ > > > > but I didn't bother sync. > > > > Bugzilla is still live but if it will go down we will lose a lot. I would > > > > like a dump of Bugzilla but nobody will give it to me. > > That's not true. We simply need to figure out how to do this. :-) > > You can rest assured that we want everything to be handed over and > > everything to go well with NetBeans in Apache. > > Gj > > > I could scrap the whole site but I don't have the time. > > > > I think I started archiving older builds (ie http://services.netbeans.org/ > > > > downloads/dev.php ) on OSUOSL but I don't remember how far along I got > > > > with that. It would be nice to preserve any historical release at least. I > > > > don't believe they are truly mirrored anywhere. > > > > There's also articles and such but some of those might be migrated (?). > > > > The wiki has been migrated. > > > > --emi > > > > ‐‐‐ Original Message ‐‐‐ > > > > On 11 July 2018 8:10 PM, Peter Nabbefeld peter.nabbef...@gmx.de wrote: > > > > > Hello, > > > > > > I wonder what will happen to earlier versions of NetBeans - will there > > > > > > any be available for longer time, or will hg repository etc. be closed > > > > > > completely and probably removed? > > > > > > Kind regards > > > > > > Peter > > > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > > > > For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org > > > > For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: JigSaw-ing NetBeans?
In the 1st idea if everything is static you don't need lookup listeners perhaps, you don't need module.install, etc. Probably doesn't gain you much except realise NetBeans would work without our specific module system. The 2nd ides is about compiling at runtime. If an user never touches a feature it remains source code on disk. The stuff that gets used gets compiled at first module load by the module system. Many modules are simple and just need javac and the dependencies JARs in the classpath, it might work. Also not a big feature but it might make things interesting. What if fixing a small bug is just applying a .patch to the IDEs own source code which will get recompiled on restart? Odd, right? --emi ‐‐‐ Original Message ‐‐‐ On 21 July 2018 10:59 AM, Geertjan Wielenga wrote: > Cool thought experiments. It would be interesting to explore -- although I > > wonder how much real performance gains there'd be with the first approach, > > i.e., one of the best features of NetBeans is its modularity, if we were to > > explore dropping that, or creating some kind of distribution without that, > > would we gain anything -- and if that would be performance, would that be > > significant enough to warrant all the work involved? The second approach is > > basically what we have right now in Apache NetBeans Git, i.e., the 9.0-vc3 > > tag can be cloned by anyone and then built from scratch. > > Gj > > On Sat, Jul 21, 2018 at 9:10 AM, Emilian Bold < > > emilian.b...@protonmail.ch.invalid> wrote: > > > I've been wondering the other way: what if we rip out all the module > > > > system and have a single fat JAR for NetBeans? How much can we optimise if > > > > we know there will be no runtime module enable/disable, no layer changes, > > > > no global services showing up, etc? > > > > How many plugins do users really install? What if they generally install 0 > > > > modules? > > > > On the other side of the spectrum: could we perhaps distribute most > > > > modules are source code and compile on the fly? What if we have a small > > > > binary bootstrap and the obvious dependency on javac and just make the > > > > whole release a big source tar? Would certainly make 'convenience binaries' > > > > a thing of the past. > > > > --emi > > > > ‐‐‐ Original Message ‐‐‐ > > > > On 14 July 2018 2:35 AM, Laszlo Kishalmi laszlo.kisha...@gmail.com > > > > wrote: > > > > > Well this question is to Jaroslav Tulach mostly. > > > > > > From Java 9 there are three modularization system in Java. OSGI, > > > > > > NetBeans and Java's JigSaw. > > > > > > My question is could NetBeans be ported on JigSaw? What would we gain > > > > > > form that movement (if any), and what would be the pain points. > > > > > > I'd even would like to see a deep analysis on this topic on Jarda's blog. > > > > > > Thank you in advance! > > > > > > Laszlo Kishalmi > > > > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > > > > > For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org > > > > For additional commands, e-mail: dev-h...@netbeans.incubator.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.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Public vs. Friend API?
How do you get more input about the API if the consumer can unilaterally ask for access? --emi ‐‐‐ Original Message ‐‐‐ On 21 July 2018 12:43 PM, Neil C Smith wrote: > On Sat, 21 Jul 2018, 08:59 Geertjan Wielenga, > > geertjan.wiele...@googlemail.com.invalid wrote: > > > +1 > > > > On Sat, Jul 21, 2018 at 9:01 AM, Emilian Bold < > > > > emilian.b...@protonmail.ch.invalid> wrote: > > > > > I think you are annoyed by friend APIs just because nobody cared through > > > > > > time about those APIs to bring them to a public API. > > ... > > > > Note that the Friend API is not only for NetBeans! ... I understand the > > > > > > frustration but it's a frustration with the NetBeans codebase, not the > > > > > > concept itself. > > Well, to balance things out, -1. :-) > > I personally am frustrated precisely with the concept itself, at least for > > non-stable APIs. IMO it's the wrong way around. It should be for the > > consumer of an API to request unstable access, not the provider to grant > > it. Which incidentally is probably a good way of getting more input into > > the evolution of the API? > > A non-stable API in NetBeans is also stable for the release it's in AFAIK. > > Best wishes, > > Neil > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [VOTE] Release Apache NetBeans 9.0 (incubating) [vote candidate 2]
+1 2018-07-21 18:08 GMT+02:00 Oliver Rettig : > +1 > Oliver Rettig >> > Hi all, >> > >> > Please vote on releasing Apache NetBeans 9.0 (incubating)! >> > >> > If this voting candidate passes, another similar voting will be started on >> > gene...@incubator.apache.org, and if that passes too, then we can release >> > this version. This build will also undergo validation through NetCAT. >> > >> > Apache NetBeans 9.0 (incubating) constitutes all the modules in the Apache >> > NetBeans Git repo, which together provide the NetBeans Platform (i.e., >> > the underlying application framework), as well as all the modules that >> > provide the Java SE-related features of Apache NetBeans. >> > >> > In short, Apache NetBeans 9.0 (incubating) is a full IDE for Java SE >> > development. >> > >> > Build artifacts available here: >> > >> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbe >> > ans-java/incubating-9.0-vc2 >> > >> > The specific artifact to be voted on: >> > >> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbe >> > ans-java/incubating-9.0-vc2/incubating-netbeans-java-9.0-source.zip >> > >> > Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and >> > NOTICE files, as well as a README file with build instructions, which are >> > the same as these: >> > >> > https://github.com/apache/incubator-netbeans/blob/master/README.md >> > >> > SHA1: 2a54b34a343fc720c5983d48ef41467163f1a6f0 >> > >> > KEYS file: >> > >> > https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS >> > >> > Apache NetBeans Git Repo tag: 9.0-vc2 : >> > >> > https://github.com/apache/incubator-netbeans/tree/9.0-vc2 >> > >> > Note: NetBeans license violation checks are managed via the >> > rat-exclusions.txt file: >> > >> > https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclu >> > sions.txt >> > >> > Rat report shows no unknown licenses, except for license files: >> > >> > https://builds.apache.org/job/incubator-netbeans-release/328/artifact/rat-> >> > > java-temp/nbbuild/build/rat-report.txt >> > >> > Included as a convenience binary, not relevant for the voting purposes >> > (unzip it, run it and you'll see Apache NetBeans): >> > >> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbe >> > ans-java/incubating-9.0-vc2/incubating-netbeans-java-9.0-bin.zip >> > >> > Also included as a convenience binary the NBMs: >> > >> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbe >> > ans-java/incubating-9.0-vc2/nbms >> > >> > New & Noteworthy features of the 9.0 Release: >> > >> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+N >> > ew+and+Noteworthy >> > >> > Release specific wiki page: >> > >> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+F >> > inal+Release -- Boris Heithecker - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Apache NetBeans Apress Book
Emilian: Efforts al almost done thanks to the dedicated work don past months by the community. Of which non of us get paid for that, either because of it is part of our daily procedure, either because it is in the nature of human beings to help one each other. . The leader of this project, named printed and digital book [ physical object ] should unify and resolve any difference in style , allowing each author to write and collab without restriction. We are all adults and this is not a personal project, but a community driven project. Every author must know the limits, characters, and styles the book requires. Before she/he sends or writes one sub chapter. The book is a companion ,a gift, to a community and to an audience. In writing a book, besides the legal property rights, which method of license you may know if you ever have signed a professional contract with a software development company. Not sure if “bumby” defines a great and crafted piece written by a collection of experts . Josh: There is also pending the offers of translators, I guess Chinese mandarin, german, Spanish are on the way. Cheers Some of the chapters proposed and defined by Gert, are already covered and written in past efforts. Delfi Ramirez Segonquart Studio https://segonquart.net From: Emilian Bold Sent: 21 July 2018 08:39 To: dev@netbeans.incubator.apache.org Subject: Re: Apache NetBeans Apress Book I would be interested in a book but I'm curious what kind of effort this involves? How much time does a book generally take (I know, it's not an exact science, but any time range helps)? If we publish a book as a group we should think about the fact that the tone / style of each chapter might come out differently. Perhaps the editor takes care of unifying this? Also, some people might drop out. I assume there is no real money to be made in books, correct? I also doubt it makes much business sense even as a self-promotion, so it's more a labour of love. --emi ‐‐‐ Original Message ‐‐‐ On 17 July 2018 11:58 PM, Josh Juneau wrote: > I've just briefly touched base with Apress on the idea and the editor I spoke > to sounds very interested. He says that they can divide the book up amongst > any number of authors, and also do bylines for each of the chapters so that > the respective authors will be noted. Typically in this situation there is > one person who acts as the lead on the project. That way the editors and > project coordinators at Apress can work with the lead, rather than all of the > separate authors. > > Anyone interested in taking lead on the book? If so then I can get you in > touch with the editor and we can get the details of each author/chapter, etc. > worked out. > > Thanks > > Josh Juneau > > juneau...@gmail.com > > http://jj-blogger.blogspot.com > > https://www.apress.com/index.php/author/author/view/id/1866 > > > On Jul 17, 2018, at 3:40 AM, Delfi Ramirez del...@delfiramirez.info wrote: > > > > +1 Huang Kai > > > > A wonder of myself to the community. Is there exist any intention or > > interest to include JSF in the topics -- chapters, subchapters -- of the > > book? > > > > Cheers > > > > Delfi Ramirez > > > > Segonquart Studio > > > > https://segonquart.net > > > > From: huang kai > > > > Sent: 17 July 2018 10:30 > > > > To: dev@netbeans.incubator.apache.org > > > > Subject: Re: Apache NetBeans Apress Book > > > > Hi, all > > > > I live in china and have been using netbeans for swing and java ee dev > > > > for about 10 years. I think I can help translate the book to chinese, > > > > let's make this great platform speading more faster. > > > > cheers. > > > > Kain Huang > > > > > On 7/16/2018 7:53 PM, Delfi Ramirez wrote: > > > > > > Hi All: > > > > > > Agreed there is the need of a chapter-by-chapter community written book. > > > > > > Count me in. Even if there is the need for the book, once written, of a > > > single translator for the whole community content. > > > > > > Even everyone of us has English as a mother tongue or second tongue, we > > > may able to reach and target new markets and new loyal fellows in this > > > world wide world we live in > > > > > > Cheers > > > > > > Delfi Ramirez > > > > > > Segonquart Studio > > > > > > https://segonquart.net > > > > > > From: Oliver Rettig > > > > > > Sent: 16 July 2018 13:47 > > > > > > To: dev@netbeans.incubator.apache.org > > > > > > Subject: Re: Apache NetBeans Apress Book > > > > > > Hi all, > > > > > > I like the idea of a community-written book very much. This can encourage > > > people to join > > > > > > our great community and it show that netbeans is now a apache project ... > > > For me the > > > > > > community is one of the most important facts to work with netbeans and > > > rarely with eclipse. > > > > > > I have some experience with writing a book for Tomcat 5: > > > > > > https://www.rheinwerk-verlag.de/tomcat-5_700/ > > > > > > and the
Re: [VOTE] Release Apache NetBeans 9.0 (incubating) [vote candidate 3]
+1 On Sat, Jul 21, 2018 at 2:54 PM ldes...@gmail.com wrote: > +1 > > On 2018/07/08 09:40:32, Emilian Bold > wrote: > > Hi all, > > > > Please vote on releasing Apache NetBeans 9.0 (incubating)! > > > > If this voting candidate passes, another similar voting will be started > on gene...@incubator.apache.org, and if that passes too, then we can > release this version. This build will also undergo validation through > NetCAT. > > > > Apache NetBeans 9.0 (incubating) constitutes all the modules in the > Apache NetBeans Git repo, which together provide the NetBeans Platform > (i.e., the underlying application framework), as well as all the modules > that provide the Java SE-related features of Apache NetBeans. > > > > In short, Apache NetBeans 9.0 (incubating) is a full IDE for Java SE > development. > > > > Build artifacts available here: > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-vc3 > > > > The specific artifact to be voted on: > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-vc3/incubating-netbeans-java-9.0-source.zip > > > > Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and > NOTICE files, as well as a README file with build instructions, which are > the same as these: > > > > > https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git;a=blob_plain;f=README.md;h=eccd3c6cc707ba9ca219bcfb72979435d85f5f7a;hb=97904961e496383d6150aef9b78fa8dff8f3e1ce > > > > SHA1: ed2098c173460ec81f05635055066da06a7ea82b > > > > KEYS file: > > > > https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS > > > > Apache NetBeans Git Repo tag: 9.0-vc3 : > > > > > https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git;a=tag;h=refs/tags/9.0-vc3 > > > > Note: NetBeans license violation checks are managed via the > rat-exclusions.txt file: > > > > > https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git;a=blob;f=nbbuild/rat-exclusions.txt;h=36cb8a3eae40bd7fc41c63c6055bce42f7916859;hb=97904961e496383d6150aef9b78fa8dff8f3e1ce > > > > Rat report shows no unknown licenses, except for license files: > > > > > https://builds.apache.org/job/incubator-netbeans-release/334/artifact/rat-java-temp/nbbuild/build/rat-report.txt > > > > Included as a convenience binary, not relevant for the voting purposes > (unzip it, run it and you'll see Apache NetBeans): > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-vc3/incubating-netbeans-java-9.0-bin.zip > > > > Also included as a convenience binary the NBMs: > > > > > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-vc3/nbms > > > > New & Noteworthy features of the 9.0 Release: > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+New+and+Noteworthy > > > > Release specific wiki page: > > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Final+Release > > > > How (and what) to try out the release: > > > > 1. Download the artifact to be voted on and unzip it. > > 2. Verify the cryptographic signatures, the NOTICE and LICENSE file > > 3. Build it using the README provided by the artifact. > > 4. Look in nbbuild/netbeans for the NetBeans installation created by the > build process. > > 5. Run the NetBeans executable and (if you're running on JDK 8) you'll > be prompted to install nb-javac, after agreeing to its licensing terms, and > (if you're running on JDK 9), you'll be able to use javac directly from JDK > 9 and, optionally, you'll be prompted to install nb-javac, after agreeing > to its licensing terms. > > > > If the above succeeds, i.e., Apache NetBeans installs and starts up vote > +1 in this thread. > > > > Note that according to > http://www.apache.org/legal/release-policy.html#release-approval : > > > > > Before casting +1 binding votes, individuals are REQUIRED to download > all > > > signed source code packages onto their own hardware, verify that they > meet > > > all requirements of ASF policy on releases as described below, > validate all > > > cryptographic signatures, compile as provided, and test the result on > their > > > own platform. > > > > Please try out the package, using the instructions above, and vote! > > > > The vote is open for a minimum of 72 hours or until the necessary number > of votes (3 binding +1s) is reached. > > > > [ ] +1 Release this package as Apache NetBeans 9.0 (incubating) > > [ ] 0 I don't feel strongly about it, but I'm okay with the release > > [ ] -1 Do not release this package because... > > > > Please add "(binding)" if your vote is binding, i.e., you are an Apache > NetBeans PPMC member, i.e., your name is on this page: > http://home.apache.org/committers-by-project.html#netbeans , although > note the only real binding votes in the incubator are those of the IPMC, > i.e., in the next vote thread, after this one passes. > >
