Well you�re certainly right... those config files could be a mess if
you don�t establish a good version control policy.
We�ve been working with winCVS since we begun our projects, it has been
quite good for the matter...
The tool is just one thing, we usually distribute the job in different
areas of development. So that way not many people actually touch the
main config files including the famous struts-config.xml. But in your
case it doesn�t look like a way. The idea is that you can let your
people use CVS (graphic client or command line based) but let them
never forget that every time you want to commit your changes to the
file, you MUST do an update to it before. CVS will merge the version
you create with the version in the repository and will announce you the
conflicts.
So the steps for succesful version control on a file are:
1) checkout/edit the file
2) make your changes
3) update
4) solve your conflicts locally
5) commit the file!
Hope this could help you....
Bye
Jorge Ivan Suarez Murillo
Web Applications Engineer
Commexnet.
Medellin, Colombia
----- Mensaje original -----
De: Valeriy Zavidnoy <[EMAIL PROTECTED]>
Fecha: Mi�rcoles, Julio 4, 2001 4:03 pm
Asunto: Team development with struts
> Our team is starting to use Struts, that means each developer
> needs to edit
> struts-config.xml and *.properties files. The issue we encountered
> is that
> several guys (12-15) want to edit these getting huge files at the
> same time.
> Of course, we are using currently source control by VSS, we
> thought about
> moving to CVS, but it won't completely let us avoid a headache.
> Can anyone give a suggestion how to solve this?
> Thanks.
>
___________________________________________________________________
Consigue tu e-mail gratuito TERRA.COM.CO
Haz click en http://www1.terra.com.co/correo
