Re: [ee4j-community] Glassfish 5.0 compatibility

[Mark Little <mlittle@xxxxxxxxxx>]

I think we have to maintain the current package names for everything
which is imported from Oracle.

Future usage of javax is problematical and the argument that not using
it means we're somehow now "Java EE" any more is right - this isn't
Java EE, it's EE4J or XYZ, where XYZ is the as-yet-to-be-defined
brand. We can come up with something new to use in place of javax if
necessary and whilst it might be nice to have, I don't want to spend
valuable time and energy debating this when the real issues are around
adding new specifications to the mix, evolving those which exist (and
which can use javax), and doing much more rapid innovation and
releases.

Mark.


On Tue, Oct 3, 2017 at 4:36 PM, John Clingan <jclingan@xxxxxxxxxx> wrote:
> 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@xxxxxxxxxxxxxxxxxxxxxx>
> 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
>