[ee4j-community] Glassfish 5.0 compatibility

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[ee4j-community] Glassfish 5.0 compatibility

From: Emmanuel Bernard <ebernard@xxxxxxxxxx>
Date: Tue, 3 Oct 2017 02:09:25 -0400 (EDT)
Delivered-to: ee4j-community@xxxxxxxxxxx
Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com CDD3E7E437
List-archive: <https://dev.eclipse.org/mailman/private/ee4j-community>
List-help: <mailto:ee4j-community-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/ee4j-community>, <mailto:ee4j-community-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/ee4j-community>, <mailto:ee4j-community-request@eclipse.org?subject=unsubscribe>
Thread-index: /+LdVvunnyV+NHyaEuyssgWht0b/1A==
Thread-topic: Glassfish 5.0 compatibility

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

Follow-Ups:
- Re: [ee4j-community] Glassfish 5.0 compatibility
  - From: Mark Little

Prev by Date: Re: [ee4j-community] EE4J PMC
Next by Date: [ee4j-community] Incorporation of other specifications
Previous by thread: [ee4j-community] EE4J PMC
Next by thread: Re: [ee4j-community] Glassfish 5.0 compatibility
Index(es):
- Date
- Thread

Breadcrumbs