Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] EE4J project name for legacy components

I personally prefer Stable as legacy is a little negative.


If they have been formally deprecated we could use


Eclipse Project for Deprecated APIs




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.




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



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.



  • 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?




ee4j-pmc mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


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

Back to the top