Re: [mojarra-dev] [jakartaee-platform-dev] Removing JSP support from Fac

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

There are indeed several cases. Removing (sub) APIs fully, or modifying APIs that will be kept and remove and/or change within those APIs deprecated methods.

I know what Rudy means with "arbitrary methods", but just to clarify for everyone to be sure: these methods are not arbitrary in the true sense of the word as they are all marked as deprecated, many for well over a decade.

What this looks like can be seen in the master branch of Mojarra, where we did exactly this some time ago.

Kind regards,

Arjan

On Fri, Nov 22, 2019 at 7:37 AM Rudy De Busscher <rdebusscher@xxxxxxxxx> wrote:

From the feeling that I have from the discussions is that we are going to deprecate/remove whole specs but not arbitrary API methods within a Spec which is kept within Jakarta EE 9. (I think this was even mentioned in the Jakarta EE Platform weekly call last Tuesday)

The Main goal of this Jakarta EE 9 release must be the namespace conversion but removing some long time deprecated things. (as there is no need to change the packages for those as it will likely not evolve in the future)

And important to remember is that although a specification is removed from JakartaEE, it still can be included by vendors to support backwards compatibility.

Rudy

On Thu, 21 Nov 2019 at 20:53, carlos andres de la rosa <kusanagi12002@xxxxxxxxx> wrote:

Yes i agree with bill is necesary to define a deprecation policy base on different factors like usege in the community backwards  compatibility etc..

Imho

On Thu, 21 Nov 2019, 20:50 Bill Shannon, <bill.shannon@xxxxxxxxxx> wrote:

Whether and how to make incompatible changes, such as removing parts of APIs or dropping specific requirements, is still an open issue to be discussed.  We need some platform-level policy on how to use "deprecated for removal", for example.

The dropping of "legacy" APIs from the platform for Jakarta EE 9 is being handled as a special case.

Guillermo González de Agüero wrote on 11/21/19 9:18 AM:

Hi,

(Please note I'm only talking about JSP in Jakarta Server Faces, not JSP the standalone technology)

JSP on Jakarta Server Faces is planned to be dropped on 3.0 but since we are already pruning the oldest part of EJB, would it make to do this cleanup from the Faces spec?

Regards,

Guillermo González de Agüero

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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

_______________________________________________
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