Hi Mark, > -----Original Message----- why > is that directory specified in the project.xml? Same for the > test source directory. > > Hope this clarifies my questions...
Mhm. Many open source project commit only unit testes code to repository. So I guess it's necessary to put theses into the project descriptor. CVS is used very pragmatic: Everybody checks out. The first that checks in wins. The other's have to deal with conflicts, but even here cvs helps with diffs. Into a local - not distributed team - you may use the cvs edit option and watches that keeps you informed about a couple of source files. I used the M$ Visual Source Safe in Studio 6.0 days. This source control system is _not_ concurrent, which is a shame. At lunch time some developers go away for one or two ours and forget to checkin her sources, and the keept looked. This is awfull scenario for everyone having to deal with teams larger that two. And this his how Maven and Ant are use. The work on a checked out version. CVS supports many freezing features like tags or branches, so it's totally cool. Would you like a build tool integrated into a source control system? Bye Toby -- To unsubscribe, e-mail: <mailto:turbine-maven-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-maven-user-help@;jakarta.apache.org>
