| Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9 |
|
Deprecating or deleting a specification doesn’t just make it disappear. All it does is say that it is not necessary to implement the specification to claim Jakarta EE 9 Full profile compliance. Any
vendor can still include a deprecated or deleted specification in their product.
Any specification can still evolve within the Eclipse Foundation if people are willing to drive the specification forward even if we decide it is not included in the Jakarta EE 9 profiles. Steve From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Tibor Digana So that deprecating or deleting something means that all the vendors of application servers should be informed beforehand. Removing some important spec like JSR-109 means that it might be missing for the vendor. Definitely the specs have
to be updated. If the Jakarta EE wants to prune the EAR archive then it has to be made in JSR-109 as well. I would personally agree on all the list except the JSR-109 and there is a reason - dependent specifications. Updating the specs is just fine. On Mon, Nov 25, 2019 at 11:02 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:
|