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 was assuming that each repo was a separate project.

> On May 10, 2019, at 9:12 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
> 
> An Eclipse project may contain multiple repos.  I'm not so worried about the
> split between repos as I am the split between projects.
> 
> Scott Stark wrote on 5/10/19 8:04 AM:
>> 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.
>> 



Back to the top