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

Bug 1069193

Summary:	Release maven artifacts with correct version numbers
Product:	[Retired] oVirt	Reporter:	Juan Hernández <juan.hernandez>
Component:	ovirt-engine-core	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.4	CC:	acathrow, alonbl, dcaroest, dfediuck, eedri, gklein, iheim, knesenko, sbonazzo, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-3.4.0-ga	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-31 12:26:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1024889

Description Juan Hernández 2014-02-24 12:56:33 UTC

Currently our release process generates maven artifacts that contain incorrect versions. For example, the artifacts generated for 3.3.1, 3.3.2, and 3.3.3 all have 3.3.0 as the version number.

This makes it impossible to trust the artifacts deployed to local maven repository, and also makes it impossible to publish the artifacts to public repositories.

Please fix the release process so that the resulting maven artifacts have correct version numbers.

Comment 1 Sandro Bonazzola 2014-03-04 10:34:18 UTC

Still need work on 3.4.0 branch, moving back to assigned

Comment 2 Sandro Bonazzola 2014-03-31 12:26:26 UTC

this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released