1. 2022-02-28 [2] =?utf-8?q?=5BGitHub=5D_=5Bws-wss4j=5D_rsearls_opened_a_new_pull_request_ ws-general GitBox 2. 2022-02-28 [1] =?utf-8?q?=5BGitHub=5D_=5Bws-wss4j=5D_coheigea_commented_on_a_change_in_ ws-general GitBox 3. 2022-02-18 [3] =?utf-8?q?=5BGitHub=5D_=5Bws-wss4j=5D_dependabot=5Bbot=5D_commented_on_p ws-general GitBox 4. 2022-02-18 [4] [VOTE] - Release Apache WSS4J 2.4.1 ws-general Colm O hEigeartaigh 5. 2022-02-18 [1] =?utf-8?q?=5BGitHub=5D_=5Bws-wss4j=5D_free2create_commented_on_pull_requ ws-general GitBox 6. 2022-02-15 [4] [jira] [Updated] (WSS-693) Check for CVE/CVSS scores and fail build is s ws-general Jira 7. 2022-02-15 [1] =?utf-8?q?=5BGitHub=5D_=5Bws-wss4j=5D_free2create_opened_a_new_pull_requ ws-general GitBox 8. 2022-02-15 [1] [jira] [Commented] (WSS-693) Check for CVE/CVSS scores and fail build is ws-general Jira 9. 2022-02-15 [1] [jira] [Created] (WSS-693) Check for CVE/CVSS scores and fail build is s ws-general Jira 10. 2022-02-15 [2] Should WSS4J fail release builds for High CVE findings ? ws-general Colm O hEigeartaigh 11. 2022-02-10 [5] [jira] [Commented] (WSS-692) Timestamp of content in jar-files are inval ws-general Jira 12. 2022-02-10 [3] [jira] [Comment Edited] (WSS-692) Timestamp of content in jar-files are ws-general Jira 13. 2022-02-10 [5] [jira] [Updated] (WSS-692) Timestamp of content in jar-files are invalid ws-general Jira 14. 2022-02-10 [1] [jira] [Resolved] (WSS-692) Timestamp of content in jar-files are invali ws-general Jira 15. 2022-02-10 [1] [jira] [Created] (WSS-692) Timestamp of content in jar-files are invalid ws-general Jira 16. 2022-02-08 [1] [jira] [Closed] (WSS-691) WSSecSignature.build(Crypto) does not work cor ws-general Jira 17. 2022-02-08 [1] [jira] [Created] (WSS-691) WSSecSignature.build(Crypto) does not work co ws-general Jira