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

Since the top-level project is still EE4J, I'd prefer "Eclipse Project for Stable EE4J APIs".  But, I can be overruled...  :-)

Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

From:        Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>
To:        ee4j-pmc@xxxxxxxxxxx
Date:        03/15/2018 09:42 AM
Subject:        Re: [ee4j-pmc] EE4J project name for legacy components
Sent by:        ee4j-pmc-bounces@xxxxxxxxxxx

At the risk of being unhelpfully pedantic, is "Eclipse Project for Stable EE4J APIs" accurate? Should it be "Eclipse Project for Stable Jakarta EE APIs"?

Feel free to ignore this if its unhelpful or just plain wrong.

On 2018-03-15 10:35 AM, Wayne Beaton wrote:

+1 for something that at least indicates that we're talking about EE4J projects.

#3 has a nice ring to it.


On Thu, Mar 15, 2018 at 10:02 AM, Mark Little <mlittle@xxxxxxxxxx> wrote:
Kevin, you're right in that it's too generic as it stands. I like option 3.

On Thu, Mar 15, 2018 at 1:06 PM, Kevin Sutter <
sutter@xxxxxxxxxx> wrote:
> I like the word "Stable" as well, but don't we need more than just "Eclipse
> Project for Stable APIs"?  It's too generic.  There is nothing to indicate
> which top-level project we are referring to.  Are these stable apis for the
> Eclipse IDE, or stable apis for Eclipse OpenJ9, or Eclipse EMF, or what?
> So, I think we need some qualifier to indicate the parent top-level project.
> Something like...
> Eclipse Project for Enterprise Stable APIs
> Eclipse Project for Stable Enterprise APIs
> Eclipse Project for Stable EE4J APIs
> Eclipse Enterprise Stable APIs
> EE4J Stable APIs
> ---------------------------------------------------
> Kevin Sutter
> STSM, MicroProfile and Java EE architect
> e-mail: 
sutter@xxxxxxxxxx     Twitter:  @kwsutter
> phone: tl-553-3620 (office),
> LinkedIn:
> From:        Mark Little <
> To:        EE4J PMC Discussions <
> Date:        03/15/2018 07:28 AM
> Subject:        Re: [ee4j-pmc] EE4J project name for legacy components
> Sent by:       
> ________________________________
> +1
> On 15 Mar 2018, at 12:08, Steve Millidge (Payara)
> 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 <
> 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
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top