Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Specification vs. API+implementation projects
I've created a board for tracking the restructuring issues specific to each of the Eclipse Project.

https://github.com/orgs/eclipse-ee4j/projects/13

I'm adding cards to the board as I encounter projects and am converting those cards into issues in the repository related to the project. I'm still tinkering with the specific form of these issues (e.g. the checklist).


I've created a card for JSF; I'm not quite sure which repository to create an issue in, but I'll sort that out next week when I look at it.

Wayne

On Fri, May 24, 2019 at 12:59 PM Arjan Tijms <arjan.tijms@xxxxxxxxxxx> wrote:


From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Scott Stark <sstark@xxxxxxxxxx>
Sent: 10 May 2019 16:04
To: Jakarta specification committee
Subject: Re: [jakarta.ee-spec.committee] Specification vs. API+implementation projects
 
Hi,

On Fri, Apr 19, 2019 at 5:11 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> There's a few cases where the API is not separate from the implementation
> and can't easily be separated.  What do we want to do for these cases?
[...]
> If I remember right, this is an issue for JavaMail, JAF, JSONP, and JSF.
> I know that JavaMail and JAF will never be split.

It's indeed the case for JSF and discussions have already started on how to go forward with splitting this, which is absolutely the intend.

Kind regards,
Arjan
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Back to the top