-
Task
-
Resolution: Done
-
Major
-
None
-
None
After upgrading to Jakarta Mail 2.1.3, it is no longer required to make the Jakarta Mail services available on the Thread Context Class Loader. That was a requirement due to https://github.com/jakartaee/mail-api/issues/665
As such, we did some tweaks that allowed us to circumvent the issue see related Jiras.
The task here is rollback those changes that are no longer required.
- is related to
-
WFLY-17350 Custom mail providers are not loaded
- Closed
-
WFLY-17470 Default Mail Provider fails to load
- Closed
- is triggered by
-
WFLY-19092 Upgrade Jakarta Mail from 2.1.2 to 2.1.3
- Closed