Bug 1303949 - The database-service-{version}.jar should be deployed based on path reference
Summary: The database-service-{version}.jar should be deployed based on path reference
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Configuration, Deployment
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.3.0
Assignee: Van Halbert
QA Contact: Filip Elias
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 13:42 UTC by Van Halbert
Modified: 2016-08-24 11:40 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-24 11:40:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.