[
https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5394:
-------------------------------------
It does not work with -vdb.xml, -vdb.ddl, and a zip with -vdb.ddl
It does not work with zip or plain version -vdb.ddl file, I will add a filter to
include those. -vdb.xml works. Basically, it needs an unzipped VDB contents under
"src" directory, where it scans for any -vdb.xml file, and rest of the all the
files including the subdirectories are added as is. If we are adding a previous version of
the .vdb archive that contains either a -vdb.xml or -vdb.ddl the contents must be in
exploded format for this project.
{code}
src
/main
/vdb
sample-vdb.xml
/ddl
model1.ddl
model2.ddl
/misc
foo.txt
{code}
But I think we should limit the VDB import to -vdb.xml files, we can do .ddl but those are
in seperate admin objects, we will come back for this at later point if we need to.
we do also have visibility overrides to deal with
Do you mean
model visibilities?
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.2
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)