Absolute path information stored in .eap file

[Ellis]

Dear Sparx,

I've worked with the code generation feature to create custom Matlab code from a UML representation of a variety of models.  One problem I've had in maintaining the .eap file is that the absolute path information for my generated code is stored within the .eap file.  This works fine until I need to send the file to another developer or generate code on another machine.  Once I send this file to another machine I am forced to update the code generation file locations for all the classes in my diagram, which is very time consuming. (Hit f11 for code generation, then update the Source Code file location)

Currently the only method I've found for circumventing this is to export the entire project to XML, then find and replace the path root directory for all the files in the project.  I then reimport the xml file back into the project to update the generated code locations.  It seems as though there should be an easier way to do this...

1) Are there any other ways to update the source code path information other than the methods I've described?
2) Would it not make sense to store the autocoded file path locations relative to the .eap project file location, rather than storing the absolute path information for the autocoded files?
3) Am I not using the .eap project file in its intended way by performing revision history on it using a CVS/SVN?  Currently it is maintained as one of the project files we are storing in our repository, along with all of the generated source code exported out the UML models...

Thanks in advance for any advice on these topics!
Ellis King
CS Draper Laboratory
Houston TX

[«Midnight»]

Hi Ellis,

The news isn't good, but nor is the situation hopeless. EA really does like to persist the path you provide, as you provide it. This is the root of your problem.

There is a partial solution, which can often be enough, provided you are willing to meet EA in the middle somewhere. Look up Local Paths in the EA help. Be persistent, as the subject appears in several different places and forms.

Once you've got the general idea, search the forum for a lot more information. Many users have taken this problem on, and while not all issues were resolved, there are many success stories. If you are willing to accept some constraints on configuration - particularly in shared projects - then you'll likely be able to get something working.

Your end result might not be perfect, but it will almost certainly be more palatable than what you are doing now; that seems to be what you are looking for.

David

PS: Once you've done what you can with local paths, you'll be in a much better position to make feature requests to Sparx on this matter.