[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5394:
---------------------------------------
Including a dependency to a vdb would look like:
{code}
<dependency>
<groupId>org.teiid.thorntail</groupId>
<artifactId>salesforce-as-datasource</artifactId>
<version>1.0.0</version>
<type>vdb</type>
</dependency>
{code}
This is redundant with the vdb import statement in the vdb.xml/ddl, but makes it easy to
include the vdb in the m2repo of thorntail. I'll see how easy it is to trigger a
deployment from there. A vdb created by the maven plugin does include the config yaml,
but I'm not sure how easy it will be to use or if everything would effectively need to
be re-declared in the importing vdb config yaml.
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)