Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] JCP and existing specs

Mark,

 

I did not say what the PMC must do. I am neither part of the PMC nor of its supervising institution.

 

I just share my personal understanding of the current *de-facto* situation and how I understood the words told by PMC members and Eclipse Foundation officials earlier this year. If that understanding is wrong, I'd kindly like to ask Mike, Ivar, and Oracle to tell clear answer the following questions *here and now*, so we all share the same vision:

 

*As of today* who is legally able to publish new versions of official Java standards, in particular Java SE and Java EE? I assume only the JCP.

 

*As of today* who is legally able to change this? I assume only Oracle.

 

*As of today* are there actual plans to shutdown the JCP or move Java standardization to other organizations? I assume not.

 

If these assumptions are wrong, the officials (not some members) shoud correct me *now*. As a JCP EG member we need that answers *now* because David Delabassee told us at the EclipseCon EE4J panel that *for now* we shall go on with our work *at the JCP*. The Expert Groups do not stop their current work just because the PMC still discusses the future or cannot agree on a common statement. The JCP EGs are neither officially dissolved nor suspened and I wonder by which JCP bylaw this should happen in short term?

 

Thanks

-Marks

 

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mark Little
Sent: Freitag, 1. Dezember 2017 12:10
To: EE4J community discussions
Subject: Re: [ee4j-community] JCP and existing specs

 

Markus, please do not jump to conclusions or make statements about what the PMC must do or has said. As a JCP EC member I can also tell you this is something which we will be discussing there too in the coming months.

 

Mark.

 

 

On 1 Dec 2017, at 11:07, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

 

I just explained that one minute ago. De-Facto the EE4J PMC has no other choice, as no other organization right now and in near future is able or legally allowed to *standardize* (= provide an official norm) anything in the Java universe due to Oracles trademark rights. Yes, the PMC can say "EE4J is a standard" but this is not an *official* Java standard then; it would simply be an Eclipse product, not more. Neither can the PMC do anything against it if the JCP EC decides to say "EE4J is hereby officially standardized as Java EE 9".

                                                      

-Markus

 

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Mark Little
Sent: Freitag, 1. Dezember 2017 11:48
To: EE4J community discussions
Subject: Re: [ee4j-community] JCP and existing specs

 

It hasn’t been declared as far as I can recall and I’m on the EE4J PMC :)

 

Mark.

 

 

On 1 Dec 2017, at 09:07, Scott Stark <sstark@xxxxxxxxxx> wrote:

 

Where has this been declared? It certainly is not defined in the https://projects.eclipse.org/projects/ee4j/charter, and frankly flies in the face of moving things to Eclipse.

 

On Fri, Dec 1, 2017 at 12:23 AM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

Leo, this is not true. The EE4J PMC multiply explained that future versions of existing specs will be developed at the Eclipse Foundation, but *will* be standardized still through the JCP.

-Markus

 

From: ee4j-community-bounces@xxxxxxxxxxx [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Leonardo Lima
Sent: Donnerstag, 30. November 2017 19:46
To: EE4J community discussions
Subject: Re: [ee4j-community] JCP and existing specs

 

Hello, Guillermo.

 

"Does it mean existing specs will need to be continued on the JCP after the Eclipse donation?"

 

My understanding is that this means that there might be Maintenance Releases of these JSRs fixing bugs or updating the JCP version, for example.

 

New versions of the Java EE / EE4J Specs would *not* be done thru the JCP.

 

Regards,

Leo.

 

 

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

 

---

Mark Little

 

JBoss, by Red Hat

Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork.
Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873
Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA)

 

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

 

---

Mark Little

 

JBoss, by Red Hat

Registered Address: Red Hat Ltd, 6700 Cork Airport Business Park, Kinsale Road, Co. Cork.
Registered in the Companies Registration Office, Parnell House, 14 Parnell Square, Dublin 1, Ireland, No.304873
Directors:Michael Cunningham (USA), Vicky Wiseman (USA), Michael O'Neill, Keith Phelan, Matt Parson (USA)

 


Back to the top