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

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


Back to the top