One problem we experienced is that VAJ, upon extract to a CVS workspace,
would re-format the entire source file. This plays havac with CVS's
concept of simultaneous editing of the same file by different
developers, i.e. the probability of merge conflicts goes up
dramatically. This could force you to adopt CVS's optional check-out
mode - don't know what you call it.
-Chuck
-----Original Message-----
From: rdelaney [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 30, 2000 7:12 AM
To: Info-Cvs
Cc: rdelaney
Subject: CVS and Visual Age for Java
Hello all,
We are evaluating CVS as a repository for our development
environment
and we would like to see about using it as a backend for our Visual Age
for
Java tool. Has anyone out there had any success or headaches in
implementing it with Visual Age. Thanks.
Ray Delaney
Provident Mutual
IT Department
E-Mail: [EMAIL PROTECTED]
phone: 302-452-4017
Cell Phone: 302-354-5751
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
