[MODLOGINKC-2] Upgrade to Spring 3.2 Created: 02/Jan/24  Updated: 11/Jan/24  Resolved: 11/Jan/24

Status: Closed
Project: mod-login-keycloak
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Craig McNally Assignee: Oleksandr Oliinyk
Resolution: Done Votes: 0
Labels: back-end, epam-eureka, eureka-phase4, need-review
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones MODROLESKC-22 Upgrade to Spring 3.2 Closed
Defines
defines UXPROD-4605 Component Ownership In Progress
Gantt End to Start
has to be done after FOLSPRINGS-141 Upgrade deps for Quesnelia: Spring Bo... Closed
Sprint: Eureka Sprint 43
Story Points: 1
Development Team: Eureka

 Description   

The official version of Spring for Quesnelia is 3.2 (see https://folio-org.atlassian.net/wiki/display/TC/Quesnelia).  We need to upgrade mod-login-keycloak modules to this version. I believe these modules don't have direct dependencies on spring, but instead get spring via folio-spring-support.  So this is really about upgrading to a newer version of that framework.

Scope:

  • mod-login-keycloak


 Comments   
Comment by Craig McNally [ 02/Jan/24 ]

Natalia Zaitseva we probably should re-estimate after splitting the original issue since the 3 SP was for all mod-*-keycloak modules combined.

Generated at Thu Feb 08 22:31:43 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.