Right now, it seems we're comfortable with JDK 11 and PHP, though we'd be very happy for Jakarta EE, Groovy, and JavaScript to be included -- assuming people step up for real beyond sending e-mails about this. I.e., Junichi has clearly taken the leadership in terms of PHP and we're in a good state here, if the same can be done for other clusters and soon, then let's include those too for the November release, otherwise focus on those for the next quarter, i.e., February 2019.
That said, here's the starting point for the Wiki for Apache NetBeans 10: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10 Please populate the above (e.g., put anything in the Miscellaneous page that's not directly applicable to PHP and JDK 11) with your enhancements, features, and significant bug fixes. Thanks, Gj On Tue, Sep 18, 2018 at 10:00 AM, Geertjan Wielenga < [email protected]> wrote: > Well, cool, and sorry for forgetting about that, Emmanuel. > > Could you put together everything you have done in this area? > > Have you put everything you've done as pull requests into the Apache > NetBeans GitHub repo? > > How far off are we from having Java EE 8 support right now, i.e., what > would that entail? > > Sure, if we can take a swing at it and have clear direction and the time > to do it for the November release, let's do it. > > Gj > > On Tue, Sep 18, 2018 at 9:09 AM, ehsavoie <[email protected]> > wrote: > >> Hi, >> I'm almost sure that i wrote some changes since 8.2 and I have more for >> WildFly that have been resting in my local repo for a year. >> Also we don't have support for javaEE8 so no Jakarta EE :( >> We really should take a swing at this because this is coming back to me a >> lot this lack of 'native' support for JavaEE in NetBeans >> ---------- >> Emmanuel Hugonnet >> http://www.ehsavoie.com >> http://twitter.com/ehsavoie >> >> >> On Tue, Sep 18, 2018 at 6:11 AM Geertjan Wielenga >> <[email protected]> wrote: >> >> > Hi all, >> > >> > Some (e.g., Josh) have argued we should include the enterprise cluster >> in >> > the upcoming release to support Jakarta EE. >> > >> > One point to realize here is that no development has been done in this >> area >> > and the functionality in GitHub right now is identical to that provided >> by >> > 8.2 plugins. >> > >> > However, the challenges we’re going to run into probably with >> > licensing-related issues, plus the simple fact that the enterprise >> cluster >> > is large and will add time in reviewing the release, might argue against >> > including it, and instead support Jakarta EE by including the 8.2 update >> > center registration in the release to simplify finding and installing >> the >> > related plugins. >> > >> > Plus maybe we could rename the too general name ‘enterprise’ with >> ‘jakarta’ >> > or ‘jakartaee’ as the name of the cluster, to make it clearer what it >> > contains, and to explicitly support Jakarta EE. >> > >> > Gj >> > >> > >
