Mark Fortner wrote: > Apache Commons VFS supports the kind of multi-file system approach that > you mention. There's been some working on providing pluggable support > for version control systems as a file system. Although I haven't seen > what the current state of the implementation is. I have used the WebDAV > support and written an NFS plugin for it. I don't recall whether the > API has any support for file locking though.
My feeling is that we should not try to integrate ArgoUML with any revision control system. I don't know of any other applications that do this, other than IDEs that work on multiple files. To do so would be an unnecessary maintenance headache. It is very likely that we would find problems with different SCM systems, and we'd have to sort these out. We'd also risk the possibility that if any SCM system modified it's working copy format in a way that was incompatible with our integration, ArgoUML would be unusable for those users until we fixed it. Lets leave if for the SCM system to mark read only files as read only at the filesystem level. At the moment, (at least in WinXP) when a user tries to save to a read only .zargo file, they get the message: ------------------------------------- File not writable A problem occurred while saving: file cannot be written. [OK] ------------------------------------- We should provide facility to display "[Read-Only]" in the title bar (c.f. ms excel) to alert the user that file on disc is read only, but not actually block them from editing it. They may after all be intending to save to a different filename. We could possibly make the above error message slightly more descriptive, but as far as SCM integration goes, we should do no more. Back to the original topic... Marcos Aurélio wrote: > What's the problem of working with the same zargo file with different > instances of ArgoUML at the same time? The problem is that changes saved by the first instance are silently overwritten when the second instance is saved. This becomes more serious when the instances are being run by different users over the network, and they have no knowledge of eachother. Adding a file lock to prevent (or at least warn of) multiple editing is a good idea, and I agree with Linus about using whatever we can from the JVM to do this, so that we have less to do, both now and in the future. Dave ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1468199 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
