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

[Scott Stark <sstark@xxxxxxxxxx>]

I think I agree, but the formatting of the repos seems a little broken
in the msg, so let me restate what I'm agreeing to:

1. The preferred separation of specification project repos:
1.1 A distinct specification only repo
1.2 A distinct TCK repo
1.3 A distinct API repo
1.4 A distinct implementation or library repo where a library could be
only a partial implementation or some optional helper classes

In the event that 1.3/1.4 are not readily doable, they may be combined.

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