Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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
Sent: 25 November 2019 10:13
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

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:

Sorry I don’t understand the comment?

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Tibor Digana
Sent: 25 November 2019 10:00
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

Steve,

 

We are not important. It's not done for us!

 

Cheers

Tibor17

 

On Mon, Nov 25, 2019 at 10:53 AM Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx> wrote:

Hi Kenji,

 

As Alasdair says is there some subset you can agree on for pruning? Also as Bill says in response to my comment on making JAX-WS optional what’s the practical difference between optional in Jakarta EE 9 and available as an updated spec outside of the Jakarta EE 9 full profile?

 

Steve

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Alasdair Nottingham
Sent: 24 November 2019 14:34
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

Is there some subset of this list you think could be pruned?

Alasdair Nottingham

 

On Nov 24, 2019, at 12:19 AM, "kzr@xxxxxxxxxxx" <kzr@xxxxxxxxxxx> wrote:



-1

 

Our customers use some of APIs heavily.

I know some of you insist that these APIs will not evolve and these must be handled by vendors’ products.

But  in order to promote Jakarta EE, I prefer keep some APIs in the specifications (as optional or profile or whatever).   

 

-Kenji Kazumura

 

 

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx [mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] On Behalf Of Steve Millidge (Payara)
Sent: Monday, November 18, 2019 1:56 AM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: [jakartaee-platform-dev] VOTE: Specifications to Prune in Jakarta EE 9

 

See previous email for context.

 

All committers please vote on this proposal for specifications to be pruned from the Jakarta EE 9 platform specifications.

 

The following specifications will be *removed* from Jakarta EE 9 Full profile specification.

 

- Jakarta XML Registries JSR 93

- Jakarta XML RPC  JSR 101

- Jakarta Deployment JSR 88

- Jakarta Management JSR 77 note this was not optional or deprecated in Java EE 8

- Jakarta Enterprise Bean entity beans – Note this is old style CMP and BMP entity beans NOT JPA Entities

- Jakarta Enterprise Bean interoperability

- Jakarta Enterprise Bean 2.x and 1.x client view

- Jakarta Enterprise Web Services  JSR 109

 

Please vote by reply with +1, 0, -1 in accordance with the Eclipse Development Process.

 

Thanks


Steve

_______________________________________________
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


Back to the top