[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5394:
-------------------------------------
Instead of thinking like loading all the import vdbs, why not flatten the importing vdb
with others at build time? That way we do not have to change deployment semantics. The
config yaml is included when the Throntail's uberjar maven task is run, so that would
be external to the vdb maven plugin, at least right now.
Define how to utilize multiple vdbs
-----------------------------------
Key: TEIID-5394
URL:
https://issues.jboss.org/browse/TEIID-5394
Project: Teiid
Issue Type: Sub-task
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 11.1
Perhaps to support vdb imports, we should define how a build can incorporate multiple
vdbs.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)