[BUILD-1181] Manage Kotlin dependencies in bom Created: 02/Nov/23  Updated: 07/Feb/24  Resolved: 02/Nov/23

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: BOM 6.2.41

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLIMG-336 Magnolia is not working with webp images Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Team: Foundation
Work Started:

 Description   

Kotlin dependencies are used by some of our modules (e.g. external-dams) or pulled in transitively by other 3rd party dependencies. This may cause issues with conflicting versions ending up in Magnolia webapps, like the incident with a recent webp-imageio update (depending on Kotlin 1.9.x) which stopped working on some customers' setups due to an older, incompatible Kotlin version in the classpath pulled in by some Magnolia module.

Let's manage Kotlin in bom so to have a predictable version in all Magnolia's webapps.



 Comments   
Comment by Federico Grilli [ 02/Nov/23 ]

Release notes: this should fix the known 6.2.40 issue mentioned at https://docs.magnolia-cms.com/product-docs/6.2/Releases/Release-notes-for-Magnolia-CMS-6.2.40/Magnolia-6.2.40-known-issues.html#_workaround meaning no need for the workaround as of 6.2.41

Generated at Sun Feb 11 23:48:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.