Why do you think merges are preferable to concurrent files with different names (just wondering, not I'm not saying you are wrong ;) ?
Apart from being able to "own" the file you are working on completely, I see another benefit of concurrent files in being able to subdivide the validation.xml into manageable parts. Since the validation for a single form can be quite lengthy when specified in XML I imagine a large project would generate a large file making it harder to use (I might be wrong though;). //Linus "Axel Seinsche" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Linus Nikander wrote: > > >Is it possible to use multiple validation.xml files concurrently ? We're > >about to launch a fairly large project and I see issues where one developer > >has validation.xml checked out when another one needs to edit it as a > >possible problem. > > > >//Linus Nikander - > > > > > > > If you use CVS it should be no problem to have file which is edited by > two persons at one time. As XML files are text-only files CVS can do > merges. We are using this for our projects too and don't have any > difficulties. I don't think it's a good alternative that you will create > several XML files. > > Axel Our name has changed. Please update your address book to the following format: "[EMAIL PROTECTED]". This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
