Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Is there a 1-to-1 association between Specification Projects and Specifications?

I finally got around to reading the proposed Scope Statement for the Platform project (sorry, Bill) and I see that this topic was also addressed there -- the need to support multiple Specifications.  In this case -- Full Platform/Profile, Web Profile, and Java Beans.  So, just in case, somebody was going to argue in support of the 1-to-1 mapping, we have multiple instances where that rule would cause even more effort...  Thanks.

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta 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:        "Kevin Sutter" <sutter@xxxxxxxxxx>
To:        "Jakarta specification committee" <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:        06/10/2019 02:35 PM
Subject:        [EXTERNAL] [jakarta.ee-spec.committee] Is there a 1-to-1 association between Specification Projects and Specifications?
Sent by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx




Hi,
This came up during the review of the Stable API project rename exercise:  
https://github.com/eclipse-ee4j/jakartaee-platform/issues/11

In a nutshell, is there a requirement that only a single technology Specification be generated by a Specification Project?  For this particular example, the Stable API Project currently has five Java EE technologies.  Are we going to be required to create five separate Specification Projects?  I hope not.  Even though this Stable API project may be a unique example, there have been examples in the past where producing multiple Specifications by a single Expert Group was deemed fruitful (EJB and JPA).  Eventually, JPA became it's own project, but it started off as as separate specification under the EJB expert group.


I've browsed through the EFSP and I don't see where this is a requirement.  It's kind of implied based on the wording and perceptions, but I didn't find anything that required this 1-to-1 mapping.  
In the Issue above, I asked Wayne about it, but maybe this is a question for the wider Spec Committee.  Thanks.

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn:
https://www.linkedin.com/in/kevinwsutter_______________________________________________
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




Back to the top