Re: [jakarta.ee-spec.committee] Specification vs. API+implementation pro

[Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>]

I see no problem with Bill's suggestion of

Spec Project: spec document repo; TCK repo (eventually)
API+Impl Project: API+impl repo

On Fri, Apr 19, 2019 at 7: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?

The prototypical split would be:

Spec Project: spec document repo; TCK repo (eventually); API repo
Impl Project: impl repo

The choices for these hard to split cases seem to be:

Spec Project: spec document repo; TCK repo (eventually)
API+Impl Project: API+impl repo

or

Spec Project: spec document repo; TCK repo (eventually); API+impl repo

Which is better?

I prefer the latter, although we could choose on a case by case basis.


If I remember right, this is an issue for JavaMail, JAF, JSONP, and JSF.
I know that JavaMail and JAF will never be split.
_______________________________________________
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

--

Richard Monson-Haefel

https://twitter.com/rmonson

https://www.tomitribe.com/