Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] EE4J Project Proposals
Sebastian,

As far as I can tell, the general idea is to handle specs, TCKs, and implementations, each on their own.

No process has been yet determined for any of them, though. 

We're currently trying to decide a brand for one of the components (the umbrella spec that will contain all the other specs), and these are pretty much the first (less than a) dozen projects that have been entered to EE4J, in order to do whatever we need to migrate them. This will, probably, involve a lot of code refactoring, and documentation being written or shuffled, as we try to move these projects into the new structure.


On the "Eclipse" naming issue, my understanding of the foundation's project naming conventions is that you are not under any obligation of adding the "Eclipse" brand to the project name. When referencing the project, however, it's strongly suggested it be done with the brand as the first word.
"Project Name", Eclipse "Project Name", "Project Name" Project, and Eclipse "Project Name" Project are stated to be interchangeable at will (at least for most situations).

Mariano Amar

Senior Consultant

email/hangouts: mariano.amar@xxxxxxxxxx
skype: marianoamar

AVISO DE CONFIDENCIALIDAD DE CORREO ELECTRÓNICO

Esta comunicación contiene información que es confidencial y también puede contener información privilegiada. Es para uso exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta que cualquier distribución, copia o uso de esta comunicación o la información que contiene está estrictamente prohibida. Si usted ha recibido esta comunicación por error por favor notifíquelo por correo electrónico(info@xxxxxxxxxx) o por teléfono (+54 11 3249 7503)

This communication contains information that is confidential and may also be privileged. It is for the exclusive use of the recipient. If you are not the intended note that any distribution, copying or use of this communication or the information it contains is strictly prohibited. If you have received this communication in error please notify us by email(info@xxxxxxxxxx) or phone (+54 11 3249 7503)


On Tue, Nov 21, 2017 at 3:51 PM, Sebastian Daschner <mail@xxxxxxxxxxxxxxxxxxxxxx> wrote:

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. 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, or on my blog post.

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@eclipse-foundation.org
(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://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


Back to the top