Re: [ee4j-pmc] EE4J project name for legacy components

["Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>]

I personally prefer Stable as legacy is a little negative.

 

If they have been formally deprecated we could use

 

Eclipse Project for Deprecated APIs

 

Steve

 

From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx> On Behalf Of Ivar Grimstad
Sent: 15 March 2018 11:58
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: Re: [ee4j-pmc] EE4J project name for legacy components

 

 

Eclipse Project for Stable APIs?

Eclipse Project for Sustained APIs?

 

I am also good with Legacy.

 

Ivar

 

On Thu, Mar 15, 2018 at 11:59 AM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:

Hi,

 

We agreed on the last PMC meeting that we will move legacy components listed below to a new project. We need to decide about this project name. I am starting this thread to discuss it.

 

Components:

• Eclipse Project for Enterprise Management
• Eclipse Project for Enterprise Deployment
• Eclipse Project for JAX-RPC
• Eclipse Project for WADL
• Eclipse Project for JAXR

I am proposing Eclipse Project for legacy APIs. WDYT? Other options?

 

Thanks,

Dmitry

_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc

--

Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader