Well, you should never use the SVN code for production work, but it's an especially bad idea now because I've just committed changes to the persistence mechanism to support both profiles and external file references. I don't know of any problems which will corrupt projects, but it would be a good idea to save a copy of any project that you are going to work on, at least for the next few days.
All references to profile items now use HREFs instead of copying the element into the user's project. We also preserve external references when saving files (they used to disappear). The other thing that has changed is that we no longer uncompress, concatenate, write, and re-read every .zargo file before reading it. This convoluted process is only used if the file needs upgrading to a new persistence version. This should improve open performance, particularly for large projects. There is a problem with the persistence upgrade code right now, but I should have that fixed on Friday. For now, it won't read any old projects, but it should do fine with anything from recent versions. It should also read anything that it saves. If you find any case where this isn't true, please save the file for me and report the problem. Next steps: - Allow users to import projects/xmi files as read-only, so they can be used for external references. Currently only profiles can be used for new external references. - Integrate with new project management code Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
