Bug 1185853 - [RFE] Don't require live engine to generate Java SDK code
Summary: [RFE] Don't require live engine to generate Java SDK code
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-sdk-java
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ovirt-3.6.0-rc
: 3.6.0.0
Assignee: Juan Hernández
QA Contact: Karolína Hajná
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-26 12:50 UTC by Juan Hernández
Modified: 2016-02-02 09:45 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-sdk-java-3.6.0.0-0.7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-02 09:45:51 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 37283 0 master MERGED codegen: Extract metadata from Maven artifacts Never

Description Juan Hernández 2015-01-26 12:50:47 UTC 
Currently the code of the SDK is generated from metadata extracted from a live engine. This means that the person generating this code needs to build and start the engine in order to generate the code. This is specially problematic and error prone when there are several versions of the engine/sdk that need to be managed, for example 3.3.4, 3.4.0 and 3.5.0.

Version 3.5.0 of the engine has already been modified so that it generates the required metadata during the build process, and includes it in the generated maven artifacts.

This bug is about modifying the SDK build process so that it takes the metadata from a specific version of the engine maven artifacts.
Comment 1 Red Hat Bugzilla Rules Engine 2015-10-18 08:34:21 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 2 Pavel Stehlik 2016-02-02 09:45:51 UTC 
Closing older BZs, if still happened, please reopen.
Note You need to log in before you can comment on or make changes to this bug.