Version Control of Packages

[Dave.B]

I have found at least three ways of arriving at a package under version control (I'm using ClearCase and an MySQL repository) that by default result in three different results.

• Add package to model with "add to version control" selected results in an XMI file with a hex GUID file name located in the root of the VCS model location folder.
• Add package without "add to version control" selected and then subsequently (under package control) use "add branch to version control" results in an XMI file with a hex GUID file name located in a sub-folder off the root of the VCS model location folder that is named "eax" where "x" is the first digit from the XMI's file name. This also results in a .eab file also being generated in the model's root folder.
• Add package without "add to version control" selected and then subsequently (under package control) use "check in branch" results in an XMI file with the packages literal name as the file name located in the root of the VCS model location folder.

The result is, that as each user is finding these different ways of doing the same thing, that our version control repository is getting in to a mess!

Is this a bug or a feature!

Dave B.