Re: [jakartaee-platform-dev] Rename Jakarta EE 9 to 8.1, introduce the J

[Tibor Digana <tibordigana@xxxxxxxxxx>]

One may say that EE deployment is slow with the old fashion deployment using WAR files.

I would say that we can utilize the CDI Phases and pause the container right after the Beans Discovery on the Cloud.

Then the paused Docker container can be copied and started many times.

This all was achieved with pure WAR without the EE container in it because the Container made all optimizations on the Cloud side.

So, this was the next idea for the Cloud solutions with EE.

On Tue, Nov 19, 2019 at 12:15 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

On Mon, Nov 18, 2019 at 11:58 PM Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Attempting to define appropriate templates for the module-info.class files for every API in time for the Jakarta EE 9 release is probably pushing it.  Since we're trying to eliminate or limit the new features going into Jakarta EE 9, my vote would be to leave this module-info.class idea off the list. 

Absolutely, even things that seem tiny tend to add extra time, especially when it's a platform wide thing that must be coordinated with all projects.

That being said, if my proposal of going for separate Jakarta EE 9 on JDK 8 and Jakarta EE 9 on JDK 11 certifications, with the requirements for the latter released on a later date, is accepted, then we *might* consider looking at the module-info.class for that potential JDK 11 release.

Kind regards,

Arjan

 

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev