Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE

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

Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging

From: Bill Shannon <bill.shannon@xxxxxxxxxx>
Date: Tue, 16 Jan 2018 15:57:13 -0800
Delivered-to: ee4j-community@xxxxxxxxxxx
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>
User-agent: Mozilla/5.0 (X11; SunOS i86pc; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

John Hogan wrote on 01/16/18 10:35 AM:
> I do have a concern relating to item 3 in what is being communicated by
> Oracle.  If I'm understanding correctly, and future net new EE4J
> APIs/technologies cannot be placed under javax, does this mean that Oracle
> intends to develop their own new APIs under javax?  Will this result in two
> flavors of Java EE, Oracle's and EE4J's?
No, that is not Oracle's intent.

References:
- [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
  - From: will . lyons
- Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
  - From: John Hogan

Prev by Date: Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
Next by Date: Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
Previous by thread: Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
Next by thread: Re: [ee4j-community] Feedback to Joint Community Open Letter on Java EE Naming and Packaging
Index(es):
- Date
- Thread

Breadcrumbs