Allow for easy directory mapping between source and target workspace

[praqma-thi]

This is essentially incorporating the directory mapper functionalities developed at our customer into 2git.
It's proven to be a powerful tool, so I don't see why not.

I'll have to groom this further to include required details

[praqma-thi]

Johan Abildskov
Right now we'd like to tinker with the directory structure when we move to git, such that we can get to a more sane project structure at some point

But we'd simultaneously like to be able to establish a workspace that looks exactly like it does in ClearCase, because then building is trivial

I would like to be able to establish an identical workspace like in cc, based on the one that I have restructured

So what I'd like is basically for each folder that I'm flattening save the cc path and the git path into a file

Like so:

Folder structure CCUCM:
appCC1_SRC/appCC1_SRC/test.txt
appCC1_DEV/appCC1_DEV/jenkins.ini
Folder structure git:
SRC/test.txt
TEST/jenkins.ini
From which I need to establish:
build/appCC1_SRC/appCC1_SRC/test.txt
build/appCC1_DEV/appCC1_DEV/jenkins.ini

Thierry Lacour
I don't think we need to know how it was in CCUCM
as that is an obsolete VCS and ancient history
just chucking an idea

Johan Abildskov
It is basically not relevant how it was in CCUCM
but I need to automagically extract that information

Thierry Lacour
How about a mapping table
instead of flattening
you can map
appcc1_src/apcc1_src/ : TEST
and then we can reverse that

Johan Abildskov
Issue is that all components have different ( but extremely similar ) mappings
Johan Abildskov But I overall like the idea

Thierry Lacour
We can do it per migration
so a mapping table would kind of work