[
https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2834:
----------------------------------------
Wish our workflow was easier, but Designer is stuck with Eclipse, EMF and INDEXED metadata
files. All of those really manage the "workspace/project" models and associated
INDEX files. A VDB is just a snapshot of these files plus user-defined data roles and
customized properties. Applying *VDB* properties between VDBs wouldn't be a hard
feature to add. Migrating Data roles would be difficult because these roles reference
specific models, tables, columns and views.
Our longer term goal is to get all of this right with our new Teiid Tooling which
leverages the our Komodo Engine/Editor backed by a Modeshape JCR.
Local project name baked into VDB
---------------------------------
Key: TEIIDDES-2834
URL:
https://issues.jboss.org/browse/TEIIDDES-2834
Project: Teiid Designer
Issue Type: Bug
Environment: Red Hat JBoss Data Virtualization 6.2.4 on EAP patched to version
6.4.6, on Oracle Linux 6
JBoss Developer Studio 8.1.0GA with Teiid Designer
9.0.6.Final-v20160316-1409-B1242 org.teiid.designer.feature.feature.group JBoss by Red
Hat, Inc.
64-bit Windows 7 environment
Reporter: Steve Tran
With any source control tool, if I clone/checkout a VDB project, the name of the project
must match the name it was created with. All the internal references are using an
absolute path with the original project name as the root. This makes VDB projects less
portable because someone who comes in and does a git clone <git url>
<their_name> will have an unstable project unless they change <their_name> to
what the VDB is hard-coded to.
I'm seeing if there's a workaround, such as renaming the internal references, but
it looks like a lot of work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)