Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Glassfish 5.0 compatibility

There are far too many variables in play for this question to be fully answered at this point. However, if I was going to place a bet, it would be on a new namespace (not ee4j) for net new specs under the new, yet-to-be-named spec process. 

I am honestly not sure if we will ever see ee4j in a namespace. Even for projects under EE4J which are implementing code not covered by a spec, a common namespace convention would be org.eclipse.projectname. In any event that would be a decision primarily driven by the projects and the PMC themselves.

Mike Milinkovich
+1.613.220.3223

On Oct 3, 2017, at 9:02 AM, Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxx> wrote:

I agree that preserving the javax prefix even for new APIs is the most preferred option to maintain consistency and secure success of the whole platform after migration to the Eclipse foundation.

If that's not possible due to legal concerns, John's suggestion of using a new top level prefix sounds well to me. Except I would prefer some other prefix than ee4j. - maybe something like jx. or eej. To be honest, ee4j sounds like a joke to developers, more like a business acronym we all look at with despect. It's perfectly fine to use the name as a top level Eclipse project, but I would avoid using it in real API.

A compromise solution would be to allocate a fixed namespace with the javax. prefix, for example javax.ee.

I would appreciate seeking Oracle's and lawyers' opinion on these package namespaces for new specs:

 - using javax. 
 - using javax.<fixednamespace>, e.g. javax.ee.
 - using a new top-level prefix, such as eej. or ee.

I hope that Eclipse would be OK with such namespaces for API. Of course, non-API packages are a different thing and I'm perfectly OK to rename packages like org.glassfish to org.eclipse.glassfish unless it breaks some contracts.

Ondro

2017-10-03 8:45 GMT-07:00 reza_rahman <reza_rahman@xxxxxxxxx>:
I would say your assessment is entirely accurate. The concerns really speak to the continued strength of the Java and Java EE names. It would be very well received by the community if Oracle decided to make some further concessions on this subject. In particular I wonder if they can allow limited permission to just use the javax.enterprise sub-package for future specifications that come out of this effort?

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

-------- Original message --------
From: John Clingan <jclingan@xxxxxxxxxx>
Date: 10/3/17 8:36 AM (GMT-08:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Glassfish 5.0 compatibility

It's clear from various chats at JavaOne that package names are an area of concern for the Java EE community as it moves into the Eclipse Foundation.

There is a *strong* desire to keep javax even for new specifications, but there are challenges with that approach. 

The secondary "vote", if you will, is to not use org.eclipse as the top-level domain, with it getting lost in the vastness of the namespace. The most pragmatic example I heard is that some customer/user organizations limit their use of namespaces for enterprise development, and org.eclipse is too broad (and org.eclipse .ee4j, for example, isn't a solution). A top-level domain of ee4j.* could be a potential compromise.

I am not advocating any position here, just trying to gather data points and convey them here.

On Oct 3, 2017 7:52 AM, Wayne Beaton <wayne.beaton@eclipse-foundation.org> wrote:
This isn't something that we normally put in a charter.

Where possible, we expect Eclipse projects to use the org.eclipse.* namespace (e.g. org.eclipse.glassfish.*), but there are exceptions (e.g. Eclipse Vert.x). We will seek advice from the Top Level Project's Project Management Committee (PMC) regarding exceptions.

Breaking an existing community is not a great idea. Assuming that we don't run into trademark issues that cannot be resolved, I expect that existing package and class names will be preserved, at least in some cases (e.g. official and de facto APIs), and at least initially. The project team may, for example, chart out a migration path for future versions that includes some sort of compatibility layer. Again, we'll expect that the PMC will work with the projects to sort out the right solution.

HTH,

Wayne

On Tue, Oct 3, 2017 at 8:35 AM, Mark Little <mlittle@xxxxxxxxxx> wrote:
I'm pretty sure Mike mentioned this in an earlier email to the group
but package names have not be considered yet for new additions but
existing code will come across unmodified.

Mark.

On Tue, Oct 3, 2017 at 7:09 AM, Emmanuel Bernard <ebernard@xxxxxxxxxx> wrote:
> Hi everyone,
>
> The charter says
> "The initial Eclipse Enterprise for Java RI is compatible with GlassFish 5.0, and passes Java EE 8 compatibility tests transitioned to EE4J."
>
> From what I have seen for Eclipse Ceylon, package renaming for implementations is part of the on boarding process. This means that people using actual Glassfish classes (not the spec classes) would have to convert their app and thus might not be qualified as compatible. Do we want to adjust the charter or will there be a package renaming exception for Eclipse Glassfish?
> Or maybe I've misunderstood the rules altogether :)
>
> Emmanuel
> _______________________________________________
> 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



--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation


_______________________________________________
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