Hi Geertjan, I think for this release "Java EE 8" is the correct label. We do not yet have a release of "Jakarta EE 8". However, I will put in a PR once that has occurred.
I will test the Ant and Gradle based Java web projects to see how things work with the Java EE 8 integration. Thanks On Wed, Jun 19, 2019 at 6:50 AM Geertjan Wielenga <[email protected]> wrote: > That is great. > > Is "Java EE 8 Web" correct as a label or should it have "Jakarta" there in > some way instead? > > Can you check if Ant-based Java Web projects and Gradle-based Java Web > projects (new in 11.1) don't somehow magically inherit this new feature? > Probably not, but worth checking. > > Gj > > > On Wed, Jun 19, 2019 at 1:44 PM Josh Juneau <[email protected]> wrote: > > > Hi Geertjan, > > > > You are correct. The drop-down you've mentioned should now include "Java > > EE 8 Web" as an option. > > > > Additionally, if you right-click on an existing Maven Web Project using > > Java EE 7 or less, the Project Properties dialog "Run" panel now contains > > "Java EE 8 Web" as a Java EE Version. > > > > On Wed, Jun 19, 2019 at 6:36 AM Geertjan Wielenga <[email protected]> > > wrote: > > > > > Great, thanks Josh. Just to understand what this consists of -- when I > go > > > to the New Project dialog and I choose "Java with Maven" and then "Web > > > Application" and click Next, and Next again, there is a "Java EE > Version" > > > drop-down, which now has "Java EE 7 Web", "Java EE 6 Web", and "Java EE > > 5". > > > > > > Does your PR add new content to that drop-down? That's my assumption, > > > please just confirm/deny that. > > > > > > Thanks, > > > > > > Gj > > > > > > > > > On Wed, Jun 19, 2019 at 1:32 PM Josh Juneau <[email protected]> > wrote: > > > > > > > Thanks Neil, for the information. I created the PR for Java EE 8 > > > > integration, and those enhancements are specifically geared towards > > Maven > > > > projects. The PR includes the following functionality: > > > > > > > > - Ability to create a new Maven Web Project using Java EE 8 > (utilizes a > > > > Java EE 8 maven archetype) > > > > - Ability to change an existing Maven Web Project to use the Java EE > 8 > > > > Platform > > > > - Support for GlassFish 5.0.1 and GlassFish 5.1 (enhanced by adding > > > > separate identifiers in the sources for GlassFish 5 branch - gfv5ee8, > > > > rather than gfv3ee6) > > > > - IDE recognizes all Java EE 8 artifact versions, for example: JSF > 2.3 > > > > faces-config, CDI beans.xml 2.0, web.xml 4.0 > > > > > > > > +1 for merging the Payara server and micro tools integration as well. > > > > > > > > On Wed, Jun 19, 2019 at 3:53 AM Neil C Smith <[email protected]> > > > > wrote: > > > > > > > > > Hi All, > > > > > > > > > > This email follows some off-list discussion with various people > > > > > including Geertjan and the relevant contributors. The release > > > > > schedule we agreed has an open question about allowing selective > > > > > feature freeze bypass based on mailing list agreement - hence ... > > > > > > > > > > I propose we allow the pending Java EE and Payara PRs to be merged > to > > > > > master for the NB 11.1 release - > > > > > > > > > > * Incorporating new files and code modifications for adding Java > EE 8 > > > > > support. https://github.com/apache/netbeans/pull/1298 > > > > > * NP-20 Payara Server tools integration in Apache NetBeans IDE. > > > > > https://github.com/apache/netbeans/pull/1290 > > > > > * NP-20 Payara Micro tools integration in Apache NetBeans IDE. > > > > > https://github.com/apache/netbeans/pull/1297 > > > > > > > > > > One of the reasons we discussed having quarterly and non-LTS > releases > > > > > was to get things testing in the wild earlier. These partly missed > > > > > the feature freeze because of Travis issues, seem ready to merge, > and > > > > > (hopefully!) have minimal impact on existing features. > > > > > > > > > > This is a lazy consensus thread that will be open for 72hrs. You > do > > > > > not need to +1 (although you're welcome to), but do raise concerns > or > > > > > -1 if need be. Assuming this goes ahead, we can merge in time to > > sync > > > > > up and include in beta2 next Wednesday. > > > > > > > > > > My own lazy consent as release manager is also based on - > > > > > > > > > > * All tests are passing before merging (appears now to be the case) > > > > > * Merging is done before second beta (possibly a good criteria for > > > > > feature freeze bypass in general?) > > > > > * The respective contributors can commit to timely fixes in case of > > > > > issues so that this doesn't cause delay in the NB 11.1 release > > > > > schedule. > > > > > > > > > > Thanks and best wishes, > > > > > > > > > > Neil > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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 > > > > > > > > > > > > > > > > > > > > -- > > > > Josh Juneau > > > > [email protected] > > > > http://jj-blogger.blogspot.com > > > > https://www.apress.com/us/search?query=Juneau > > > > <https://www.apress.com/index.php/author/author/view/id/1866> > > > > > > > > > -- > > Josh Juneau > > [email protected] > > http://jj-blogger.blogspot.com > > https://www.apress.com/us/search?query=Juneau > > <https://www.apress.com/index.php/author/author/view/id/1866> > > > -- Josh Juneau [email protected] http://jj-blogger.blogspot.com https://www.apress.com/us/search?query=Juneau <https://www.apress.com/index.php/author/author/view/id/1866>
