[BUILD-1021] Keep our commons-beanutils fork in sync with upstream on GitHub Created: 20/Feb/23  Updated: 25/Apr/23

Status: Selected
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Issue Links:
duplicate
relation
is related to BUILD-1015 Fork apache commons-beanutils interna... Closed
is related to BUILD-1037 Turn update_git_mirrors into a magnol... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Team: Foundation
Work Started:

 Description   

As the upstream release might come out anytime (we don't know), let's not do this urgently.

Until commons-beanutils version 2 is actually released, we need to regularly pull upstream changes and reapply our coordinate changes on top.

  1. setup a Bitbucket master branch that is a sync/mirror of the official beanutils repository, as described here
  2. introduce a Jenkins job / magnolia-mgmt task (depending on implementation specifics) to do the rebase on a regular basis, and let us know in case there are changes
    1. Jenkins script? Might be difficult
    2. magnolia-mgmt task? Using JGit?

Resources


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