Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
We rely on modules2 extensively and have noticed that it is building ghost directories inside of the referenced directories. The ghost directories are empty duplicates of the top level directories. Also, it seems to be totally random as to what directories get the ghost directories. Has anyone else had this problem? And does a fix seem to be in the works? The repository structure looks fine only the occasional exceptions folder (my understanding is that these are normal). I think the problem is in the way the client is checking them out. EXAMPLE FOLLOWS If I have a module defined as: [Test.Build] Test.Sequencing Folder.1 Folder.2 Folder.3 I am getting a structure like this: Test.Build --->Test.Sequence ------>Test.Sequence ------>Folder.1 ------>Folder.2 ------>Folder.3 --->Folder.1 --->Folder.2 ------>Test.Sequence ------>Folder.1 ------>Folder.2 ------>Folder.3 --->Folder.3 ALL of the modules I am referencing are REAL modules. That means I am not referencing modules defined elsewhere in modules2. Also, we are not using the modules file at all. Thanks, Dan Pupek Software Engineer Advanced Systems Technology, Inc dpupek at astpcola.com (850) 475-4038