Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Is there a way to fix already released documentation for various SPECs?

Scott,

If I recall, there wasn't a Jakarta EE Spec. document for EJB, for Jakarta EE 8. There was a general scope statement and the JavaDocs. The only text documentation for EJB 3.2 was for Java EE 8. So, perhaps, you are presuming that the nearly zero length Spec. document was a mistake, but I don't think it was.

For Jakarta EE 8, the only detailed Spec. document that was produced was for the Platform specification. The rest were just terse "scope" statements.

-- Ed

On 12/13/2020 8:38 PM, Hussain.NM@xxxxxxxxxxxxx wrote:

Scott,

 

Can you elaborate on what you mean by “undetected build failures”?

 

Except for the platform spec, all other EE 8 Specs had placeholder documents published at that point in time.

 

Last time I checked about changing existing specification documents it requires to go through a full release review ballot.

 

Thanks

Hussain

 

From: jakartaee-platform-dev-bounces@xxxxxxxxxxx <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Marlow
Sent: Saturday, December 12, 2020 8:52 PM
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Is there a way to fix already released documentation for various SPECs?

 

On Sat, Dec 12, 2020, 9:16 AM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

Hi,

 

If someone was to step up to fix the various broken SPEC documents for various projects for EE9, would we be able to update the various https://jakarta.ee/specifications pages?

 

I am more interested in an answer for correcting EE 8 SPEC docs but would be good to have an answer for EE 9 also.

 

 

For example, https://jakarta.ee/specifications/enterprise-beans/3.2/enterprise-beans-spec-3.2.html looks like there were undetected build failures generating the html from asciidoc source. 

 

If we would accept changes via a topic branch, we could probably fix this with the community.

 

Thoughts?

 

Scott

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!KDvGdrPWZjhn4hZvnsVZbIfEkaDIBuqJM08m1mvlcHbI5fZBagu1lDL1fdAW5E8$ 

Back to the top