Possible Bug: Re-configuring package for CVS

[morsor]

I created a new project and configured 'Implementation Model' for version control with CVS, leaving it checked out.

After checking it in I removed it from version control and the XMI was gone. So far, so good.

Next, I wanted to configure it for version control again - but it failed stating 'A file by this name already exists in Version Control. Please choose another name.'

Is this expected and reasonable behavior - or caused by my ignorance of CVS, EA or both? Or is it a bug?

[Eve]

I've run into this myself and found that it's just CVS behaviour.

CVS never actually removes a file from version control, so as far is it is concerned the file still exists but is inactive.  So from that point of view it is right to say that it already exists.

[peter.zrnko]

If you have CVS controlled package in two projects and remove version control in one project, it's quite diserable to leave this package in CVS for the second project.

[morsor]

Doesn't that effectively mean that configuring a package for version control can only happen once (under that name)?

[mikewhit]

Maybe set different projects (or packages) under different root folder names, or even different branch names.

This allows same package names for different models.

It's analogous to using EA - you don't place everything in a top-level package or diagram; you have to decide on some kind of architecture in which to place things.

[peter.zrnko]

Doesn't that effectively mean that configuring a package for version control can only happen once (under that name)?

Go to CVS and delete the file manualy if realy don't need it.