Re: [ee4j-community] Glassfish 5.0 compatibility

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

Re: [ee4j-community] Glassfish 5.0 compatibility

From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 3 Oct 2017 10:08:48 -0700
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>

> On Oct 3, 2017, at 9:53 AM, Mark Little <mlittle@xxxxxxxxxx> wrote:
> 
> I think we have to maintain the current package names for everything
> which is imported from Oracle.

That is clearly true for javax package names. We are less thrilled about com.oracle usage in Eclipse projects. 

We are willing to allow intermediate invalid states. But corporate names in vendor neutral open source projects will need to be addressed at some point. 

That said, if there are truly compelling reasons for retaining the status quo, let’s discuss them.

References:
- Re: [ee4j-community] Glassfish 5.0 compatibility
  - From: John Clingan
- Re: [ee4j-community] Glassfish 5.0 compatibility
  - From: Mark Little

Prev by Date: Re: [ee4j-community] Glassfish 5.0 compatibility
Next by Date: Re: [ee4j-community] ee4j-community Digest, Vol 2, Issue 13
Previous by thread: Re: [ee4j-community] Glassfish 5.0 compatibility
Next by thread: Re: [ee4j-community] Glassfish 5.0 compatibility
Index(es):
- Date
- Thread

Breadcrumbs