[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5394:
---------------------------------------
The drawback to the build time approach is that it's not straight-forward to flatten
vdb.xml nor vdb.ddl contents. It's only straight-forward to flatten on a per schema
basis when those are captured as separate ddl files.
so that would be external to the vdb maven plugin, at least right now
From the teiid thorntail examples the project yaml is treated as a
resource that is copied into the target/classes, which is then picked up by the vdb maven
plugin for inclusion in the .vdb. Is that not what you had in mind?
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)