The idea was having the same leaders in “platform" and “stable" projects.
My proposal was to just put all of these under a new "platform"
project that represented the Jakarta EE platform, the replacement
for the Java EE platform spec and expert group. The lead for that
platform project could easily handle these never-changing APIs.
One of the concerns with putting each of these in its own project
was finding project leads for each one. So, which of you signed
up to be the project lead for the Eclipse Project for Stable EE4J
APIs"?
Dmitry Kornilov wrote on 03/15/2018
08:39 AM:
Ok. It looks like that we agreed on “Eclipse Project for Stable
EE4J APIs” name.
I’ll create a proposal and post it for review.
— Dmitry
I'm with Kevin there. The
components will be a part of the first version of
Jakarta EE, but may be removed later and live on as
stable EE4J projects.
Ivar
Mike,
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)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
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.
Wayne
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), 507-253-3620(office)
> LinkedIn: https://www.linkedin.com/in/kevinwsutter
>
>
>
> From: Mark Little <mlittle@xxxxxxxxxx>
> To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
> Date: 03/15/2018 07:28 AM
> Subject: Re: [ee4j-pmc] EE4J project
name
for legacy components
> Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
> ________________________________
>
>
>
> +1
>
> On 15 Mar 2018, at 12:08, Steve Millidge
(Payara)
> <steve.millidge@xxxxxxxxxxx>wrote:
>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ee4j-2Dpmc&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=l1KMVA1DZRuDXbqp6WcGgV4T5Rfq95kCXkp5_9PbPJ4&s=7RbULwSxrKMjmzUd-lmKYYCM17aiDRYcgRENzFNYH_c&e=
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
|
