[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-2834) Local project name baked into VDB
[
https://issues.jboss.org/browse/TEIIDDES-2834?page=com.atlassian.jira.plu...
]
Steve Tran commented on TEIIDDES-2834:
--------------------------------------
Yes correct. I spent about an hour and figured out a workaround. It involves opening up
your VDB and manually editing the vdb.xml file. Replace the old project root with the new
project root and it'll pick up the XMI locations correctly.
The XMI files themselves seemed to be out of sync though. The workaround for that is
opening each XMI file up and forcing Designer to refresh the model. This can be
accomplished by "editing" the transformation SQL (by adding a space or something
to register a change) and saving the file. So far it looks ok but I will test further and
see what happens.
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)