Prepare WebSocket project for Jakarta EE 8 Release

[m0mus]

Tasks

• [x] Update text files
• [x] Generate "boilerplate" specification project
• [x] Make a staging release
• [x] Generate Stand-alone TCK test results
• [x] Submit a PR to jakartaee/specifications repository
• [x] Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project

See here for detailed instructions.

[joakime]

Can't do the "Compatibility Certification Request" portion of jakartaee/specifications#79, as the websocket TCK zip is in a state were it can't be certified. (mentioned earlier in https://github.com/eclipse-ee4j/websocket-api/issues/295#issuecomment-518360317)

[joakime]

Opened PR eclipse-ee4j/jakartaee-api#29 for updated staged websocket version

[joakime]

From the point of view of the original 6 tasks that @m0mus filed on this issue, this issue is done.

From the point of view of the updated list of tasks since this issue was created, this issue is only about 60% done. Of the remaining tasks, they are either optional or are websocket TCK certification related.

I'll leave it up to @m0mus how he wants to treat this.

Do we close this issue? Do we move it's state to Done in https://github.com/orgs/eclipse-ee4j/projects/15? Do we just drop the remaining TCK certification issues? Do we move the remaining TCK certifications issues to a new issue in this repo? Do we move the remaining TCK certifications issues to the eclipse-ee4j/jakartaee-tck ?

[m0mus]

@joakime I agree with @dblevins about TCK. I am suggesting submitting a compatibility request. TCK gaps can be fixed after Jakarta EE 8 release unless the spec committee requests to do it now.

I am also suggesting closing this issue and create another one for the rest of incomplete tasks as you have it in your checklist.