eclipse-ee4j/angus-mail

build test fail on jdk21

Closed this issue · 2 comments

Describe the bug
My project introduced the angus-maill software, my project is running in the jdk21 environment, and there are some mistakes that happend in project build test.

[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] Errors:
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] LogManagerPropertiesTest.testCheckAccessPresent:79 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] MailHandlerTest.testChildClassLoader:214->testCallingClassLoader:228 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] MailHandlerTest.testGaeReportErrorSuper:4841 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] MailHandlerTest.testSecurityManager:4987 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] MailHandlerTest.testSetMailPropertiesClassLoader:362->testSetMailProperties:376 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] MailHandlerTest.testVerifyClassLoader:278->testVerify:321 » UnsupportedOperation The Security Manager is deprecated and will be removed in a future release
[2024/08/16 17:41:38.584 GMT+08:00] [INFO]
[2024/08/16 17:41:38.584 GMT+08:00] [ERROR] Tests run: 938, Failures: 0, Errors: 6, Skipped: 0

Looks like some methods are about to be deprecated on jdk21.But how can an error fail during the Android test? It's a little confusing.

To add, i run this test command: mvn clean package --file pom.xml -Dmaven.wagon.http.ssl.insecure=true

Looks like some methods are about to be deprecated on jdk21

Most likely an older version of the project was imported as this is fixed. #117. Most of the test methods reported here don't exist anymore.

Check dependency tree in maven to make sure there is no transitive dependencies on an older version.

I upgrade this to v2.0.3, it effects.
Thanks