]
Barry LaFond updated TEIIDDES-853:
----------------------------------
Assignee: (was: Dan Florian)
Fix Version/s: 8.0
(was: 7.4)
This is really complex. Clone Project action will allow doing some of the work to get what
Brian wanted.
The Refactor framework would have to listen for Project rename and FIX VDB's. This is
not yet implemented and is covered under TEIIDDES-505
Pushing to 8.0
Teiid artifacts should respond more gracefully to Teiid project
refactoring
---------------------------------------------------------------------------
Key: TEIIDDES-853
URL:
https://issues.jboss.org/browse/TEIIDDES-853
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.2
Environment: RHEL, JBDS jbdevstudio-linux-gtk-4.0.0.v201012070137R-H33-Beta2.jar,
SOA-P 5.1 ER5, Teiid 7.2
Reporter: Brian Fitzpatrick
Priority: Critical
Fix For: 8.0
While I was trying to figure things out with the Virtual Procedures test script, I
received a newer copy of the Parts Project from Barry that included the data files for
loading the database tables. As a result, I wanted to change the name of the Teiid Model
Project that I had created for the test.
Though the Teiid Designer Perspective (via the Model Explorer view) doesn't allow you
to rename a project, I popped over to a different perspective (the Java EE Perspective)
and renamed the project there. I was then able to import Barry's project and take a
look.
Well, I didn't realize that the VDB file (and potentially others) was hardwired to
the project name as part of the path to the .xmi files. So that threw me into several
problems I had to resolve. Eventually I did resolve them, but we need to provide some sort
of refactoring capabilities for Teiid projects and respond to those changes more
gracefully.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: