Prepare Jakarta Security for Jakarta EE 8 Release

[ivargrimstad]

Instructions

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

See here for detailed instructions.

[arjantijms]

Staging release done: https://oss.sonatype.org/content/repositories/staging/jakarta/security/enterprise/jakarta.security.enterprise-api/1.0.2/

[arjantijms]

TCK results done: summary.txt

[arjantijms]

• Spec PR 1
• Spec PR 2

[bshannon]

@arjantijms The TCK summary will need to be published someplace with more long term
stability than Jenkins job results. Also, the Spec Committee has decided that only the
top lines with totals need to be published, although you're free to publish more if you want.

[arjantijms]

@bshannon I agree, I put the link there as a quick hint. For now I've also included the results in the PR:

https://github.com/jakartaee/specifications/blob/fe081a518bf1b4dcc6807992d241dfae20d95fc2/security/1.0/tck_results_summary.txt

[bshannon]

@arjantijms I think we decided not to publish the TCK results on the spec pages, but to
keep them on some project/product-specific page. For example, I put the Jakarta Mail
TCK results on the Jakarta Mail web site.

[arjantijms]

@bshannon For now I basically followed @m0mus 's lead:

https://github.com/jakartaee/specifications/blob/aba76c7a0f2e7fb05740ca00ff4d64686139add2/jsonp/1.1/tck_results_summary.txt

I can of course remove those files and publish them elsewhere later.

[bshannon]

@arjantijms And when I finally catch up on all the PR reviewing I need to do, I'll put these comments there as well. :-)

[m0mus]

Reopening because new tasks were added.

[arjantijms]

API PR

[arjantijms]

Github pages requested

[arjantijms]

Github pages for implementation