cannot save version control configurations

[janf]

Hello!
We would like to use EA especially because of its cvs features and we are testing the trial version at the moment.
But we have a problem building up a working cvs configuration. In the "Version Control Configurations" dialogue we filled out the fields like described in the help file (Unique ID, Local Project, Current User and the CVS.EXE Path) but the "Save" button stays inactive so we cannot save and test the configuration.
Is there any further configuration we have to do that the connection to our CVS server works?

Thanks a lot!

[analia]

The same is happening to me. Another difficulty I found is that I cannot remove the CVS Explorer path once I've set one.

thanks in advance for your help.
Analía

[simon.marshall]

possibly you haven't got a working copy of the repository yet?  it isn't very clear from the docs, but the idea is to set up your repository where packages will be added to, and checkout a working copy on, e.g., your hard disk.  then, when you configure your VC settings, use the pathname to your working copy for the "local project path".

then, the idea is to create packages in EA and configure them individually to be under VC.  (you do not put your .EAP file under VC, just the packages that are within it.)

note that if you create nested packages under VC, be sure to checkout a parent package before a child package (and to checkin in reverse order).  otherwise, EA gets confused about the status of the child package.

note also that if you want to create packages under subdirectories in the repository, first time round you will have to manually "cvs add" the subdirectory yourself because EA neglects to do it.  And you will have to manually specify the path when configuring the XMI filename because the ... browse popup is broken.

as you can tell, we've had plenty of experience of this!  but we don't know when these things will be fixed, we're not really told anything.

[janf]

hi simon,

thanks for your answer,

possibly you haven't got a working copy of the repository yet?  it isn't very clear from the docs, but the idea is to set up your repository where packages will be added to, and checkout a working copy on, e.g., your hard disk.  then, when you configure your VC settings, use the pathname to your working copy for the "local project path".

I think that is exactly what we did.
First we checked out a folder. then we started a new project and used this folder as root for the project.
In the CVS configuration we chose this folder after clicking on "local project path".
Anything wrong by now?

then, the idea is to create packages in EA and configure them individually to be under VC.  (you do not put your .EAP file under VC, just the packages that are within it.)

Due to the fact we didn't get to a working CVS configuration to save we neither have the chance to put the .EAP file nor any packages under VC.

note also that if you want to create packages under subdirectories in the repository, first time round you will have to manually "cvs add" the subdirectory yourself because EA neglects to do it.  And you will have to manually specify the path when configuring the XMI filename because the ... browse popup is broken.

We would be "happy" dealing with these kind of problems.

as you can tell, we've had plenty of experience of this!  but we don't know when these things will be fixed, we're not really told anything.

I hope the support will answer our email.
It's the only thing preventing us from licensing the software!  

Jan

[simon.marshall]

hi simon,

thanks for your answer,

I think that is exactly what we did.
First we checked out a folder. then we started a new project and used this folder as root for the project.
In the CVS configuration we chose this folder after clicking on "local project path".
Anything wrong by now?
Jan

Hi Jan, I think that is correct.  Given the LPP you specify, EA should be able to determine how to connect to the repository by looking in the <LPP>\CVS\Root file, and should let you save the configuration.

You could check that the file is there and try configuring again.  You might also try leaving the LPP to last when setting the configuration options.  The popup is a bit flaky.

HTH, Simon.

[janf]

Hi!
We figured out where our problem was and infact it is not only our fault.
You have to fill out the needed fields successively and then (surprise! ) the "Save" button gets active. In fact you have to insert a Unique ID before choosing the Local Project otherwise it won't work. (Something our dear developers could fix, hm?   )

We still miss the "Check out" / "Check in" in the context menu of the packages so I think we haven't put a package under the control in the right way but hopefully we get to this soon.

Thanks for your help!

Jan