[Migrated content. Thread originally posted on 13 June 2003]

Is there a configuration example for setting up CVS source code management with AcuBench? Specifically the menu command list and fundamental source control command items. Any tips for interfacing with cvs from within AcuBench? My environment is AcuBench 5.2 with cvsnt from the WinCvs 1.3 distribution.
Thanks,
Mark

Mark,

We use cvs here with acubench and it works great. If you already have a cvs server up and running you are 90% of the way into getting your team up and going. We don't interface directly from acubench (IMO, there is no need to) but use wincvs and torioisecvs to communicate with the server. Here are the things you need to remember with using acubench and wincvs:

1. Use relative paths: this is the most important, your copypath, file-path, object file path, config file path should all be relative from the project folder. This allows you to move a project to a new foldler. Remember to clean out the copylib folders in acubench to removed the hard coded path versions.
Example: change c:\\myproject\\src to .\\src

2. The project file gets a lot of conflicts: the way acubench stores the project file does not agree with wincvs. For this reason, at our shop, only one person commits the project file to the server.

3. leave xfd files out of the repository: all generated files, including obj, lib, xfd, and data files, do not belong in the repostory.

That's it! If you follow some basic rules, you should have no problem running cvs with AcuCobol. I installed it for our manager, and he thinks it's great.

Merlin

---

[Migrated content. Thread originally posted on 13 June 2003]

Is there a configuration example for setting up CVS source code management with AcuBench? Specifically the menu command list and fundamental source control command items. Any tips for interfacing with cvs from within AcuBench? My environment is AcuBench 5.2 with cvsnt from the WinCvs 1.3 distribution.
Thanks,
Mark

Mark,

We use cvs here with acubench and it works great. If you already have a cvs server up and running you are 90% of the way into getting your team up and going. We don't interface directly from acubench (IMO, there is no need to) but use wincvs and torioisecvs to communicate with the server. Here are the things you need to remember with using acubench and wincvs:

1. Use relative paths: this is the most important, your copypath, file-path, object file path, config file path should all be relative from the project folder. This allows you to move a project to a new foldler. Remember to clean out the copylib folders in acubench to removed the hard coded path versions.
Example: change c:\\myproject\\src to .\\src

2. The project file gets a lot of conflicts: the way acubench stores the project file does not agree with wincvs. For this reason, at our shop, only one person commits the project file to the server.

3. leave xfd files out of the repository: all generated files, including obj, lib, xfd, and data files, do not belong in the repostory.

That's it! If you follow some basic rules, you should have no problem running cvs with AcuCobol. I installed it for our manager, and he thinks it's great.

Merlin

---

[Migrated content. Thread originally posted on 13 June 2003]

Is there a configuration example for setting up CVS source code management with AcuBench? Specifically the menu command list and fundamental source control command items. Any tips for interfacing with cvs from within AcuBench? My environment is AcuBench 5.2 with cvsnt from the WinCvs 1.3 distribution.
Thanks,
Mark

Mark,

We use cvs here with acubench and it works great. If you already have a cvs server up and running you are 90% of the way into getting your team up and going. We don't interface directly from acubench (IMO, there is no need to) but use wincvs and torioisecvs to communicate with the server. Here are the things you need to remember with using acubench and wincvs:

1. Use relative paths: this is the most important, your copypath, file-path, object file path, config file path should all be relative from the project folder. This allows you to move a project to a new foldler. Remember to clean out the copylib folders in acubench to removed the hard coded path versions.
Example: change c:\\myproject\\src to .\\src

2. The project file gets a lot of conflicts: the way acubench stores the project file does not agree with wincvs. For this reason, at our shop, only one person commits the project file to the server.

3. leave xfd files out of the repository: all generated files, including obj, lib, xfd, and data files, do not belong in the repostory.

That's it! If you follow some basic rules, you should have no problem running cvs with AcuCobol. I installed it for our manager, and he thinks it's great.

Merlin

---