Bug 1406751
| Summary: | [RFE] align ovirt-engine maven dependencies with WildFly 11 BOM | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Eyal Edri <eedri> |
| Component: | Build.Maven | Assignee: | Ori Liel <oliel> |
| Status: | CLOSED DEFERRED | QA Contact: | Ori Liel <oliel> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | future | CC: | bugs, juan.hernandez, lsvaty, mperina, vtunka |
| Target Milestone: | --- | Keywords: | CodeChange, FutureFeature |
| Target Release: | --- | Flags: | sbonazzo:
ovirt-4.2-
lsvaty: testing_plan_complete- |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-05 13:33:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1475459 | ||
| Bug Blocks: | |||
|
Description
Eyal Edri
2016-12-21 12:08:32 UTC
Oved - is it your team in charge of this? Can you assess the work needed, the risk and the value? Moving to Martin. (In reply to Yaniv Kaul from comment #1) > Oved - is it your team in charge of this? > Can you assess the work needed, the risk and the value? So in general we should always bump versions in pom.xml to match oldest available version in both WildFly and EAP after each significant upgrade. But in practise we do that only when needed (for example if WildFly/EAP provides some newer version of the library and we want to use those new features). Generally we don't need to do that unless backward compatibility of some library broke, so we need to rebuild engine, because on runtime we always use version provided either by WildFly/EAP or package provided by OS or custom dependency (on upstream included within engine itself, on downstream part of rhevm-dependencies). I'll try to go over our current status and update 4.1 needed. If no change required than I'd would leave it to the moment we upgrade to WildFly 11. (In reply to Martin Perina from comment #3) > (In reply to Yaniv Kaul from comment #1) > > Oved - is it your team in charge of this? > > Can you assess the work needed, the risk and the value? > > So in general we should always bump versions in pom.xml to match oldest > available version in both WildFly and EAP after each significant upgrade. > But in practise we do that only when needed (for example if WildFly/EAP > provides some newer version of the library and we want to use those new > features). Generally we don't need to do that unless backward compatibility > of some library broke, so we need to rebuild engine, because on runtime we > always use version provided either by WildFly/EAP or package provided by OS > or custom dependency (on upstream included within engine itself, on > downstream part of rhevm-dependencies). > > I'll try to go over our current status and update 4.1 needed. If no change > required than I'd would leave it to the moment we upgrade to WildFly 11. Can you update? I think WildFly 11 will come before our next release even. I will take a look what's needed in this area once we upgrade to WildFly 11 (In reply to Martin Perina from comment #5) > I will take a look what's needed in this area once we upgrade to WildFly 11 Any updates? |