[MGNLACTIVATION-130] Update dependencies as part of Bouncy Castle update Created: 21/Jun/16  Updated: 26/Jul/16  Resolved: 23/Jun/16

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6279 Update Bouncy Castle encryption libs ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Sprint: Basel 49
Story Points: 1

 Description   

The goal there is to update the Bouncy Castle versions. We could have simply bumped the libraries to 1.54, as done in main, however, it was easier to do the following QA commit: https://git.magnolia-cms.com/projects/MODULES/repos/activation/commits/934ba66e24ad71dcf7c50153de546a521c8478d2

Thereby getting the dependencies directly from main, and having them centralized there.


Generated at Sun Feb 11 22:59:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.