[BUILD-1018] Include magnolia's beanutils2 artifact as a dependency in the bom Created: 16/Feb/23  Updated: 09/Mar/23  Resolved: 01/Mar/23

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: BOM 6.3.0, BOM 6.2.30

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

Issue Links:
dependency
relation
is related to BUILD-1019 Stop managing beanutils version 1.9.... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: get rid of commons-beanutils1
Work Started:

 Description   

Context

The repo:

https://github.com/apache/commons-beanutils/

has been internally forked here

https://git.magnolia-cms.com/projects/INTERNAL/repos/commons-beanutils/browse

There is jenkins job that is running successfully (2.0.0-magnolia-SNAPSHOT)

But now, we'll need to include this dependency in the current bom, in order to start to consume it and getting rid of the old one

Expected results

The library is included in the bom. Packages from beanutils1 and 2 are not the same, so there should be no problem there.

We'll keep on managing both beanutls1 and beanutils2 in BOM for now, even though we'll remove usages of the former from all of Magnolia's codebase. Reason being custom projects may still depend on older version and removing it completely would cause consumer projects to fail at compile time. 
This grace period will likely end with Magnolia 6.3.  

Dev notes

Current gav coordinates:

<groupId>info.magnolia.beanutils2</groupId>
<artifactId>commons-beanutils2</artifactId>
<version>2.0.0-magnolia-SNAPSHOT</version> 


 Comments   
Comment by Federico Grilli [ 28/Feb/23 ]

Reopened as we're not yet ready for 6.2.29 release. Will reintroduce it in 6.2.x BOM after Magnolia release 

 

Comment by Federico Grilli [ 01/Mar/23 ]

Reintroduced managing of forked beanutils2 after release

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