Change project name to Jakarta Authorization

[ivargrimstad]

Background information:
https://waynebeaton.wordpress.com/2019/04/04/renaming-java-ee-specifications-for-jakarta-ee/

Checklist:

• GitHub
• README file
• CONTRIBUTING file
• Eclipse Project under https://projects.eclipse.org/projects/ee4j

[ivargrimstad]

Should we leave out ...Contract for Containers?

[arjantijms]

Should we leave out ...Contract for Containers?

Absolutely, though a concern was raised over at the JASPIC project that we may need to make clear that both JASPIC and JACC are not just your average user facing projects, but more of low-level core projects. I don't think "Contract for Containers" captures that in any way.

Maybe Jakarta Authorization Core or Jakarta Core Authorization, would be an option if people really feel strongly about this. Otherwise I'm personally happy with "Jakarta Authorization" and clarifying the core aspect in Javadoc.

[ggam]

+1 for Jakarta Authorization. El mié., 10 abr. 2019 21:28, Arjan Tijms <notifications@github.com> escribió:

…

Should we leave out ...Contract for Containers? Absolutely, though a concern was raised over at the JASPIC project that we may need to make clear that both JASPIC and JACC are not just your average user facing projects, but more of low-level core projects. I don't think "Contract for Containers" captures that in any way. *Maybe* Jakarta Authorization Core or Jakarta Core Authorization, would be an option if people really feel strongly about this. Otherwise I'm personally happy with "Jakarta Authorization" and clarifying the core aspect in Javadoc. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACAucMjB2DdyOtbPlCQrNOKhnYvAqVr6ks5vfjtRgaJpZM4ceao8> .

[arjantijms]

Fixed by #31