Bug 2089299 - Remove dependency on apache-commons-configuration
Summary: Remove dependency on apache-commons-configuration
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.5.0.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.5.3
: ---
Assignee: Dana
QA Contact: Guilherme Santos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-23 11:31 UTC by Martin Perina
Modified: 2023-01-05 12:22 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.5.3
Doc Type: Release Note
Doc Text:
ovirt-engine-4.5.3 and newer no longer depends on apache-commons-configuration package
Clone Of:
Environment:
Last Closed: 2022-09-19 14:31:38 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.5+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 619 0 None open Remove dependency on apache-commons-configuration 2022-08-28 18:05:57 UTC
Github oVirt ovirt-engine pull 791 0 None Merged fix setting value to engine config properties 2023-01-05 12:22:58 UTC
Github oVirt ovirt-engine pull 793 0 None open backport: fix setting value to engine config properties 2023-01-05 12:22:58 UTC
Red Hat Issue Tracker RHV-46102 0 None None None 2022-05-23 11:40:00 UTC

Description Martin Perina 2022-05-23 11:31:03 UTC 
We are using only very minimal subset of apache-commons-configuration functions in ovirt-engine. Also apache-commons-configuration depends on apache-commons-logging, which is included in maven:3.5 module in EL 8, but it was removed from newer maven:3.6 module, so it blocks the upgrade.

So it would be better for future maintainability to reimplement required functionality of commons-configuration within ovirt-engine itself.
Comment 3 Klaas Demter 2022-05-23 11:52:48 UTC 
This is important because maven 3.5 appstream went out of support this month
Comment 4 Casper (RHV QE bot) 2022-09-06 11:30:50 UTC 
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
Comment 5 Casper (RHV QE bot) 2022-09-19 14:31:38 UTC 
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.
Note You need to log in before you can comment on or make changes to this bug.