2.1.2

What's Changed

• Fixes #33 - Backport #31 to 2.1 branch by @mnriem in #35
• 2.1.1 by @arjantijms in #36
• Fixed version numbers by @dmatej in #41
• Logging revisited for version 2.1.x and GF7 by @dmatej in #44

Full Changelog: 2.1.1-RELEASE...2.1.2-RELEASE

3.0.0-M3

What's Changed

• Initial support for Jakarta Authorization 3.0.0-M1 by @arjantijms in #26
• Update versions in pom by @arjantijms in #27
• OSGi fixes - dynamic import and no static import for realm by @arjantijms in #28
• Set handlers per context id by @arjantijms in #29
• Fixes #31 - Add module-info by @mnriem in #32
• Update authorization service to always get policy from factory. by @arjantijms in #34
• Support API M2 and fix warnings by @arjantijms in #38
• Mapper instance should not be cached in the policy, as per comment by @arjantijms in #39
• Set API in Tomcat SPI impl to M2 by @arjantijms in #40
• Logging revisited for version 3.x and GF8 by @dmatej in #45
• Updates for Authorization API M3 and M4 by @arjantijms in #46

Full Changelog: 2.1.1-RELEASE...3.0.0-M3-RELEASE

3.0.0-M2

What's Changed

• Initial support for Jakarta Authorization 3.0.0-M1 by @arjantijms in #26
• Update versions in pom by @arjantijms in #27
• OSGi fixes - dynamic import and no static import for realm by @arjantijms in #28
• Set handlers per context id by @arjantijms in #29
• Fixes #31 - Add module-info by @mnriem in #32
• Update authorization service to always get policy from factory. by @arjantijms in #34
• Support API M2 and fix warnings by @arjantijms in #38
• Mapper instance should not be cached in the policy, as per comment by @arjantijms in #39
• Set API in Tomcat SPI impl to M2 by @arjantijms in #40

Full Changelog: 2.1.1-RELEASE...3.0.0-M2-RELEASE

2.1.1

What's Changed

• Master by @arjantijms in #4
• Master by @arjantijms in #10
• Move to version 2.1.0 to allign with authorization 2.1.0 by @arjantijms in #13
• Update versions in pom and allow (dynamic) javassist import. by @arjantijms in #18
• Update versions in pom and readme by @arjantijms in #20
• Source version to 8 by @arjantijms in #21
• 2.1 by @arjantijms in #22
• Fixes policy configuration state transitions in AuthorizationService by @avpinchuk in #23
• Next version is 2.1.1 by @arjantijms in #24
• Update poms by @arjantijms in #25

New Contributors

• @avpinchuk made their first contribution in #23

Full Changelog: 1.0.0-RELEASE...2.1.1-RELEASE

2.1.0-M1

Milestone release for Exousia implementation Jakarta Authorization 2.1

1.0.0

First official release of Exousia.

Exousia is a standalone implementation of Jakarta Authorization.

Exousia can be used to run Jakarta Security on Tomcat..