In the case of JMS, our intent is to
transfer everything needed for the current JMS version 2.0, as
well as the incomplete work for the proposed JMS 2.1, in case the
new project lead wants to pick it up and complete it.
John D. Ament wrote on 11/22/17 06:43 AM:
Nigel,
On
22/11/2017 12:31, John D. Ament wrote:
> One other item. I noticed that the JMS spec version
listed is for the halted JMS 2.1 spec. Is that accurate?
I didn't see that. Where was that?
I checked "Eclipse Message Service API for Java"
(https://projects.eclipse.org/proposals/eclipse-message-service-api-java).
This is described as "starting from the
specification defined by JSR 914".
That's JMS 1.1. Is this page intended to refer to the latest
released version? If so then this is JMS 2.0 (JSR 343),
which is part of Java EE 7 and 8.
I misread that. When I clicked the link for JSR-914, I
briefly scanned and saw a "2.1" which was in fact the JCP
version used. My bad. In fact, there is no specific JMS
version listed on the JSR-914 page.
Nigel
> Also, since I was formerly on the JMS spec, is it
possible to join the new Eclipse project forming around it?
>
> John
>
> On Tue, Nov 21, 2017 at 3:43 PM Bill Shannon <bill.shannon@xxxxxxxxxx
<mailto:bill.shannon@xxxxxxxxxx>>
wrote:
>
> Where we already have separate projects for the
specifications (APIs) and the implementation, they'll remain
> separate at the Eclipse Foundation. For example,
"Eclipse WebSocket API for Java" is the API specification
project
> and "Eclipse Tyrus" is the implementation project.
>
> In some cases, such as Eclipse JSON Processing, the
existing project contains both the API classes and the
> implementation classes. After the initial project
is established at Eclipse, the EE4J community can choose to
do
> the work to split that project into two projects if
desired.
>
> We've decided to rename the specification projects
from (e.g.) "Eclipse RESTful Web Services API for Java" to
> "Eclipse Project for JAX-RS". That should make it
clear what the intent of the project is, while conforming to
> Oracle trademark guidelines.
>
> Yes, the JAX-RS JSR reference is wrong; we'll fix
that.
>
> Sebastian Daschner wrote on 11/21/17 10:51 AM:
>>
>> Hi there,
>>
>> It's great to see some progress. However, there
are a few things in that announcement that puzzle me.
Apologies
>> upfront for any stupid questions, I'm just
trying to make sense out of it.
>>
>> First of all, these project proposals seem to
throw both specifications and RIs into one pot. I guess it
makes
>> sense to create Eclipse projects for
implementations such as Tyrus or Jersey. Are the
specifications also planned
>> to be incorporated as Eclipse projects? Or will
there be standardization processes, what the JSRs with EGs
are
>> today? Especially in regard to the overall
platform, which JSR 366 is today. I'm not familiar with what
is planned
>> to be the substitute for JSRs & EGs, but
maybe it makes sense for the Java EE community to see some
suggestion
>> there first.
>>
>> Do the specifications need to adopt the name
Eclipse? In the EE4J FAQ #7 it says that the intention is to
continue
>> to use the former JCP specification names, such
as 'Java API for RESTful Web Services'. I know that names
are what
>> people get religious about, but still I believe
that we should not choose some names for specifications
before the
>> name for what will succeed Java EE (e.g. Open
EE) is carved into stone. IMO 'Eclipse RESTful Web Services
API for
>> Java' is a bad substitute for JAX-RS.
>>
>> I only checked the Eclipse analog for the
JAX-RS so far, but that refers to JSR 339, which is JAX-RS
2.0, not JSR
>> 370. Since EE4J should be aligned with EE 8,
shouldn't that refer to the current specification?
>>
>> Cheers,
>> Sebastian
>> (JSR 370, 374, 382)
>>
>>
>> On 11/21/2017 05:33 PM, Mike Milinkovich wrote:
>>>
>>> All,
>>>
>>> I would like to draw your attention to fact
that nine new EE4J project proposals were recently posted on
the
>>> Eclipse Foundation's proposal page <https://www.eclipse.org/projects/project_activity.php>.
This is the first
>>> step to making the migration of Java EE to
the Eclipse Foundation a reality.
>>>
>>> The list of proposals is below. There are
more details on the proposal page
>>> <https://www.eclipse.org/projects/project_activity.php>,
or on my blog post
>>> <https://mmilinkov.wordpress.com/2017/11/21/ee4j-progress-nine-new-projects-proposed-at-the-eclipse-foundation/>.
>>>
>>> Thanks!
>>>
>>> Eclipse Tyrus
>>> Eclipse OpenMQ
>>> Eclipse Grizzly
>>> Eclipse Jersey
>>> Eclipse RESTful Web Services API for
Java
>>> Eclipse Message Service API for Java
>>> Eclipse WebSocket API for Java
>>> Eclipse Mojarra
>>> Eclipse JSON Processing
>>>
>>> --
>>> Mike Milinkovich
>>> mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
<mailto:mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>
>>> (m) +1.613.220.3223
<tel:(613)%20220-3223>
>>>
>>>
>>>
>>>
_______________________________________________
>>> ee4j-community mailing list
>>> ee4j-community@xxxxxxxxxxx
<mailto: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
>>
>>
>>
>> _______________________________________________
>> ee4j-community mailing list
>> ee4j-community@xxxxxxxxxxx
<mailto: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
>
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
<mailto: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
>
>
>
> _______________________________________________
> 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
>
_______________________________________________
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
_______________________________________________
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
|