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

• https://git.magnolia-cms.com/projects/INTERNAL/repos/nightly-cloud-validation/browse/Jenkinsfile: example of a Jenkins job with a daily cron