Yes. But right now Jakarta EE is not included for the Apache NetBeans 10 release, unless it’s ready really soob. And I would suggest not using NetBeans for Grails as a name. (Plus, is our Grails support really up to date?) Include the Groovy cluster with NetBeans for Java SE, I think, assuming we agree to include the Groovy cluster, which is not decided yet. Also, what about JavaScript, i.e., that is the ‘webcommon’ cluster, which I’d include with the PHP cluster, and name it ‘NetBeans for PHP and JavaScript’ or ‘NetBeans for Web Frontend’.
Gj On Tuesday, September 25, 2018, Laszlo Kishalmi <[email protected]> wrote: > Dear all, > > As new clusters are joining to the upcoming release, I'd like to ask if we > should follow the tradition of old NetBeans releases and generate flavor > specific binaries like: > > * NetBeans for Java SE > * NetBeans for PHP > * NetBeans for Grails > * Netbeans for Jakarta EE > > What dou you think? > >
