Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1485357

Summary: Ship ovirt-engine-sdk-java with RHV 4.2 (version 3 of the SDK)
Product: Red Hat Enterprise Virtualization Manager Reporter: Juan Hernández <juan.hernandez>
Component: ovirt-engine-sdk-javaAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: juan.hernandez, lsurette, pbrilla, srevivo, ykaul
Target Milestone: ovirt-4.2.0Keywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-sdk-java-3.6.8.0-1.el7ev Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-15 17:35:20 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:

Description Juan Hernández 2017-08-25 13:09:03 UTC
Latest build of version 3 of the Java SDK (currently 3.6.8.0) package (ovirt-engine-sdk-java) should be shipped with version 4.2 of RHV.

Comment 2 Yaniv Kaul 2017-09-04 10:35:14 UTC
Why do we need it?

Comment 3 Juan Hernández 2017-09-04 11:07:08 UTC
My understanding is that our decision was to keep version 3 of the API in 4.2, and drop it in 4.3. My understanding is also that version 3 of the API includes the API server, the SDKs and the CLI. So in that sense the answer is yes, we need it.

But if by *need* you mean if there is any other RHV component that uses the Java SDK then the answer is no.  Only the "oVirt optimizer" used to need it.

Most users of the Java SDK use it via Maven Central, not via this RPM, so most users (all that I know) don't need this RPM.

Comment 9 errata-xmlrpc 2018-05-15 17:35:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:1481

Comment 10 Franta Kust 2019-05-16 13:07:06 UTC
BZ<2>Jira Resync