[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5394: ------------------------------------- What other kinds of VDBs are you thinking about? this should handle XML VDBs with external DDL files. I am expecting the original VDB in their project's "vdb" directory for this plugin, the contents will be in exploded format. i.e. if I were to take Designer's new VDB format with ddl files, I would place them in exploded format in my maven project. I do not think we have anyone just using the just DDL based vdb. I am keeping all the configuration out of VDB layer. The previous version of the plugin by default copied the project-default.yaml file, but I commented out that for VDB building. Yes, you are correct, since we no longer have single server deployment model configuration needs to be (re)defined, I see that as an issue with this immutable deployment model than this VDB import process itself. I do not think I follow this one, you mean because we are using the maven versioning scheme? I did not realize we are doing this in the server code, will have to take peek. Should be a simple change. Same with data roles related changes looks like we need to do more introspection there than blind copy. I have explicitly not allowed the nesting of imported VDBs. IMO, it is a matter of building multiple projects on the developer side, I believe that is exactly what are you saying too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)