Bug 1303949

Summary:	The database-service-{version}.jar should be deployed based on path reference
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Van Halbert <vhalbert>
Component:	Configuration, Deployment	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Filip Elias <felias>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	aszczucz, jdurani, jolee, mbaluch, thauser, vhalbert
Target Milestone:	ER1
Target Release:	6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-24 11:40:46 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:

Comment 2 Van Halbert 2016-02-02 14:25:18 UTC

In DR1 the database-service.jar was being deployed.    However, looking at the branch that was pushed for DR2 and DR3, the scripts were changed to be path based.   Will confirm in DR3 that the changes have made their way thru, so this may no longer be an issue.

Comment 3 Van Halbert 2016-02-08 14:09:50 UTC

will change the build to product the database-service-{version}.jar without the {version}.

Comment 4 Van Halbert 2016-02-08 14:11:17 UTC

This will also include the changing of the following war's to not include the version: teiid-odata-8.12.5.redhat-1.war teiid-olingo-8.12.5.redhat-1-odata4.war

Comment 5 Juraj Duráni 2016-06-17 07:17:05 UTC

All three artifacts (odata war, odata4 war, database-service) have no longer version in the name of the file. All are defined by path in deployment section of both standalone and domain configuration files. Setting to VERIFY.