[teiid-issues] [JBoss JIRA] (TEIID-4174) Local project name baked into VDB

[Steve Tran (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198009#comment-13198009 ] 

Steve Tran commented on TEIID-4174:
-----------------------------------

Correct.  If I started the VDB project and called it steve_project1, and checked my XMI files into GIT.  The next person who wants to clone it will have to clone it as "git clone GIT_URL steve_project1".  If they don't name their cloned copy steve_project1, none of the XMI files will be able to see each other.



> Local project name baked into VDB
> ---------------------------------
>
>                 Key: TEIID-4174
>                 URL: https://issues.jboss.org/browse/TEIID-4174
>             Project: Teiid
>          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
>            Assignee: Steven Hawkins
>
> 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)