| Re: [ee4j-community] Requirements around duplicating spec jars? |
Werner
Send ee4j-community mailing list submissions to
ee4j-community@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/ee4j- community
or, via email, send a message with subject or body 'help' to
ee4j-community-request@eclipse.org
You can reach the person managing the list at
ee4j-community-owner@eclipse.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."
Today's Topics:
1. Requirements around duplicating spec jars? (John D. Ament)
2. Re: EE4J Project Proposals (Guillermo Gonz?lez de Ag?ero)
3. Re: Requirements around duplicating spec jars? (Mike Milinkovich)
4. Re: EE4J Project Proposals (reza_rahman)
------------------------------------------------------------ ----------
Message: 1
Date: Sat, 25 Nov 2017 18:51:45 +0000
From: "John D. Ament" <john.d.ament@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: [ee4j-community] Requirements around duplicating spec jars?
Message-ID:
<CAOqetn_fyiYScKycMbLLzjkKSrAoCLfX_ >kGHLmd74t8szxUc5g@mail.gmail. com
Content-Type: text/plain; charset="utf-8"
All,
Now that we have the first wave of proposals shown, I want to ask about the
spec jar requirements.
As I understand it, implementations are required to provide their own set
of spec jars for each specification under Java EE. Will this practice
continue under the to-be-named project?
If so, is it already agreed upon that additional copies of the API may be
licensed under licenses other than the license listed (EPLv2)?
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j- >community/attachments/ 20171125/a7e43834/attachment. html
------------------------------
Message: 2
Date: Sat, 25 Nov 2017 20:42:57 +0000
From: Guillermo Gonz?lez de Ag?ero <z06.guillermo@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
Message-ID:
<CAG1ZpUa1guS2khmoFTbooyxZKfLUW SAJzk=Zss_MVLGj1a=VKg@mail. gmail.com >
Content-Type: text/plain; charset="utf-8"
The September EC minutes somewhat say that existing specs will continue to
use the JCP:
https://jcp.org/aboutJava/communityprocess/ec-public/ materials/2017-09-28/JCP-EC- Meeting-Minutes-September2017. html
Perhaps that's Oracle idea for granting javax packages on donated specs
(which would work also for new ones).
Regards,
Guillermo Gonz?lez de Ag?ero
El s?b., 25 nov. 2017 18:45, Werner Keil <werner.keil@xxxxxxxxx> escribi?:
> What's also weird about JAX-RS is, that it was seemingly "forgotten" when
> all of Java EE 8 (and earlier JSRs) moved to a new place under
> https://github.com/javaee, instead it still remained in
> https://github.com/jax-rs/api
>
> What is not mentioned in the proposals of either, but seems far more
> important IMO than whether it's called "Eclipse RESTful Web Services API
> for Java", "JAX-RS" or something else is backward compatibility with the
> Java EE 8 or 7 versions of these APIs. Is the new follow-up API allowed to
> stay under "javax.ws.rs" or immediately forced to refactoring into
> something else? (like "ee4j.ws.rs", "ee.<something>.ws.rs" or e.g. "
> org.eclipse.ws.rs" just to mention some hypothetical examples)
>
> Werner
>
>
> On Sat, Nov 25, 2017 at 6:00 PM, <ee4j-community-request@eclipse.org >
> wrote:
>
>> Send ee4j-community mailing list submissions to
>> ee4j-community@xxxxxxxxxxx
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://dev.eclipse.org/mailman/listinfo/ee4j- community
>> or, via email, send a message with subject or body 'help' to
>> ee4j-community-request@eclipse.org
>>
>> You can reach the person managing the list at
>> ee4j-community-owner@eclipse.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ee4j-community digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: EE4J Project Proposals (Markus KARG)
>>
>>
>> ------------------------------------------------------------ ----------
>>
>> Message: 1
>> Date: Fri, 24 Nov 2017 18:07:49 +0100
>> From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
>> To: "'EE4J community discussions'" <ee4j-community@xxxxxxxxxxx>
>
>
>> Subject: Re: [ee4j-community] EE4J Project Proposals
>>
> Message-ID: <002a01d36546$c5179710$4f46c530$@eu>
>> Content-Type: text/plain; charset="utf-8"
>>
>> 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@eclipse.org [mailto:
>> ee4j-community-bounces@eclipse.org ] 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@eclipse-foundation.org
>> (m) +1.613.220.3223
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
> URL: <
>> https://dev.eclipse.org/mailman/private/ee4j- community/attachments/ 20171124/1c92e2e0/attachment. html
>> >
>>
>> ------------------------------
>
>
>>
>> _______________________________________________
>> 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
>>
>>
>> End of ee4j-community Digest, Vol 3, Issue 72
>> *********************************************
>>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j- >community/attachments/ 20171125/d9596a10/attachment. html
------------------------------
Message: 3
Date: Sat, 25 Nov 2017 16:51:56 -0500
From: Mike Milinkovich <mike.milinkovich@eclipse-foundation.org >
To: ee4j-community@xxxxxxxxxxx
Subject: Re: [ee4j-community] Requirements around duplicating spec
jars?
Message-ID:
<7432273c-e737-d5ec-a919-c826482d95be@eclipse- >foundation.org
Content-Type: text/plain; charset=utf-8; format=flowed
On 2017-11-25 1:51 PM, John D. Ament wrote:
> As I understand it, implementations are required to provide their own
> set of spec jars for each specification under Java EE.? Will this
> practice continue under the to-be-named project?
AFAIK, yes. Independent implementations will continue to provide their
own set of spec jars for each specification.
> If so, is it already agreed upon that additional copies of the API may
> be licensed under licenses other than the license listed (EPLv2)?
Any content derived from EE4J projects will have to be licensed in
accordance with the terms of the EPL-2.0.
Given that the EPL-2.0 with Secondary License GPL-2.0+Classpath
Exception is quite close to the existing CDDL & GPL+Classpath Exception,
the future scenario is pretty much the same as the status quo.
--
Mike Milinkovich
mike.milinkovich@eclipse-foundation.org
(m) +1.613.220.3223
------------------------------
Message: 4
Date: Sat, 25 Nov 2017 16:55:37 -0500
From: reza_rahman <reza_rahman@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
Message-ID: <mailman.273.1511646946.20429.ee4j-community@xxxxxxxxxxx >
Content-Type: text/plain; charset="utf-8"
If that's true, honestly it's good news overall. It enables keeping both the Java EE name and javax packages for everything.
The problem is that I don't know how this actually alignes with Oracle and other EE4J expectations. The impression I get is neither is keen on the JCP.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------From: Guillermo Gonz?lez de Ag?ero <z06.guillermo@xxxxxxxxx> Date: 11/25/17 3:42 PM (GMT-05:00) To: EE4J community discussions <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] EE4J Project Proposals
The September EC minutes somewhat say that existing specs will continue to use the JCP:?https://jcp.org/aboutJava/communityprocess/ec- public/materials/2017-09-28/ JCP-EC-Meeting-Minutes- September2017.html
Perhaps that's Oracle idea for granting javax packages on donated specs (which would work also for new ones).
Regards,
Guillermo Gonz?lez de Ag?ero
El s?b., 25 nov. 2017 18:45, Werner Keil <werner.keil@xxxxxxxxx> escribi?:
What's also weird about JAX-RS is, that it was seemingly "forgotten" when all of Java EE 8 (and earlier JSRs) moved to a new place underhttps://github.com/javaee, instead it still remained in https://github.com/jax-rs/api
What is not mentioned in the proposals of either, but seems far more important IMO than whether it's called "Eclipse RESTful Web Services API for Java", "JAX-RS" or something else is backward compatibility with the Java EE 8 or 7 versions of these APIs. Is the new follow-up API allowed to stay under "javax.ws.rs" or immediately forced to refactoring into something else? (like "ee4j.ws.rs", "ee.<something>.ws.rs" or e.g. "org.eclipse.ws.rs" just to mention some hypothetical examples)
Werner
On Sat, Nov 25, 2017 at 6:00 PM, <ee4j-community-request@eclipse.org > wrote:
Send ee4j-community mailing list submissions to
? ? ? ? ee4j-community@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
? ? ? ? https://dev.eclipse.org/mailman/listinfo/ee4j- community
or, via email, send a message with subject or body 'help' to
? ? ? ? ee4j-community-request@eclipse.org
You can reach the person managing the list at
? ? ? ? ee4j-community-owner@eclipse.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."
Today's Topics:
? ?1. Re: EE4J Project Proposals (Markus KARG)
------------------------------------------------------------ ----------
Message: 1
Date: Fri, 24 Nov 2017 18:07:49 +0100
From: "Markus KARG" <markus@xxxxxxxxxxxxxxx>
To: "'EE4J community discussions'" <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] EE4J Project Proposals
Message-ID: <002a01d36546$c5179710$4f46c530$@eu>
Content-Type: text/plain; charset="utf-8"
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@eclipse.org [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@eclipse-foundation.org
(m) +1.613.220.3223
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j- >community/attachments/ 20171124/1c92e2e0/attachment. html
------------------------------
_______________________________________________
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
End of ee4j-community Digest, Vol 3, Issue 72
*********************************************
_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j- >community/attachments/ 20171125/22380d28/attachment. html
------------------------------
_______________________________________________
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
End of ee4j-community Digest, Vol 3, Issue 77
*********************************************