FWIW, I had exactly the same experience as Matt. Fortunately, we were building a system from scratch, so we had the opportunity to set up naming conventions to allow us to find and use objects within types, but obviously anyone using an OOB application would be at risk of the duplicate object name condition Matt described.
Rick -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tanner, Doug Sent: Wednesday, June 06, 2007 5:33 AM To: [email protected] Subject: Re: Looking for feedback on SourceSafe Thanks Carey, Just what I needed for Management :) Doug -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: Tuesday, June 05, 2007 5:48 PM To: [email protected] Subject: Re: Looking for feedback on SourceSafe Doug, Actually as far as I know (or last I checked) ClearCase has so serious of flaws in how it works with ARS that I would call it unusable. There are workarounds to most of the issues but it is so "buggy" to impractical in my opinion. You have to have your objects names overly restricted due to trying to use ClearCase with ARS. In specific you can have an ARS form named "foo" and an Active link named "foo". ARS is fine with this as these are "separate name spaces" in ARS. However the way the ClearCase stuff works it stores a foo.def file in one directory in ClearCase. So if you check out and make a change to the Active Link last then ClearCase may think that you just changed a Form into an Active link and you "loose" the presence of the "Form" in ClearCase. (Yea technically version n-1 is a "form" and version n is an active link, but good luck trying to use that kind of a source control system to recover a system from. :) All of which are very bad things to figure out in the middle of the night when you are trying to recover a server. :( Meaning you may need to rename objects for ClearCase to even have a shot at working correctly for you at the start. And any development work going forward needs to have extra steps added to prevent corrupting your ClearCase source control due to this odd naming collision problem. ( My understanding is the root of the problem is that the Admin tool issues an MS SC API call that basically said "change directories" and ClearCase viewed that API function as "optional" or "not applicable to the ClearCase design" and they simply ignore it. Which produces the naming collision on the ClearCase side of the communication.) I would stay very far away from ClearCase for this and many other reasons. (At least as far as ARS is concerned.) My experiences were also with ClearCase on a Unix server so there were extra NFS clients and setup and bugs involved too. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 6/5/07, Tanner, Doug <[EMAIL PROTECTED]> wrote: > Well for what it is worth, ClearCase is not much (if any) better Doug ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
