]
Max Andersen updated JBIDE-7858:
--------------------------------
Fix Version/s: 3.2.0.CR1
3.2.x
Having hardcoded projects paths is bad if not validated nor refactorable, putting on CR1
for clarification and later planning since I'll assume this is not a trivial
fix/improvement to do.
Teiid artifacts should respond more gracefully to Teiid project
refactoring
---------------------------------------------------------------------------
Key: JBIDE-7858
URL:
https://issues.jboss.org/browse/JBIDE-7858
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: teiid
Affects Versions: 3.2.0.M2
Environment: RHEL, JBDS jbdevstudio-linux-gtk-4.0.0.v201012070137R-H33-Beta2.jar,
SOA-P 5.1 ER5, Teiid 7.2
Reporter: Brian Fitzpatrick
Assignee: Barry LaFond
Priority: Critical
Fix For: 3.2.0.CR1, 3.2.x
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: