[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] EE4J Project Proposals
|
This is very encouraging to hear from a company with as much leverage as IBM. Please continue to ensure the final outcome of this effort is a success for all of us. We will continue to try to do the same from the grassroots community side.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: Kevin Sutter <sutter@xxxxxxxxxx>
Date: 11/27/17 11:10 AM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
Markus and others,Watch this space (and the corresponding
proposals) for updates to the proposed project names... We are working
closely with Oracle to determine what's doable and what's not. The
proposed naming convention for the spec projects currently being discussed
should be favorable to the discussion happening here. I don't want
to jump the gun and announce anything quite yet -- just in case things
change from an Oracle perspective... As the naming convention gets
approved, then the names for the proposals will be adjusted accordingly.FYI, the RI projects will most likely
stay with the current names -- ie, Eclipse Jersey, Eclipse Grizzly, Eclipse
Mojarra, etc. It's just the spec projects that are causing a hiccup.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
"Markus KARG"
<markus@xxxxxxxxxxxxxxx>To:
"'EE4J community
discussions'" <ee4j-community@xxxxxxxxxxx>Date:
11/24/2017 11:08 AMSubject:
Re: [ee4j-community]
EE4J Project ProposalsSent by:
ee4j-community-bounces@xxxxxxxxxxx
I don't understand that new
versions of the JAX-RS specification shall be done, but at the same time
it would violate Oracle's naming rights if we call that new specification
still "JAX-RS"…?! That means, we have to rename the specification's
name? BTW, a quick search in the WIPO Global Trademark Database did not
bear any registration of the term "JAX-RS", neither by Oracle
nor by others.-Markus From: ee4j-community-bounces@xxxxxxxxxxx
[mailto:ee4j-community-bounces@xxxxxxxxxxx]
On Behalf Of Mike Milinkovich
Sent: Donnerstag, 23. November 2017 18:25
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] EE4J Project Proposals On 2017-11-23 11:58 AM, Markus
KARG wrote:What is "the corresponding
spec project"? For JAX-RS for example, Jersey is "just"
the RI, and it is just the *current* RI.
Exactly right.
In the JCP we could decide
to have future release of JAX-RS with different RIs.
It is the intent of Oracle, IBM, Red Hat, and other participants that future
versions of the JAX-RS specs will be done using a new spec process hosted
at the Eclipse Foundation.
So does that mean that from
now on the JCP must stick with Eclipse-provided *current* RIs forever?Um. no. That would be dumb. And
under the new spec process provisions will be made to allow new RIs to
appear, as well as ensuring the creation of independent implementations.
Actually I do not understand
why the API project is not simply named "JAX-RS API", the TCK
project "JAX-RS TCK" and the RI simply "Jersey"?
Because those project names would violate Oracle's trademark rights in
the "JAX-RS" name.
--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ee4j-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=3Oi4NKJGhKqSmKkywr1btn3yauiSO4yg-rFwjZscaxw&s=5aiukG0989G69NoNxmC9gI5ZcdATVzH1jZzUNauIxgo&e=