Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
The point is that cvs doesn't commit your class file, as long as it didn't changed. "Didn't change" mean, that diff signaled not changes. there is a "force commit" parameter "-f", that you may use to break this behaviour, which is by design. Olaf Raj wrote: > Well, I found a fix to this problem myself. > In the java file add one more comment line to physically add a line into > the code. > WinCVS thus recognizes that a new line is added and the class file is > physically changed. > It is now allowing the latest class file to get uploaded. > > Thanks, > > Raj. > > -----Original Message----- > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf > Of Raj > Sent: Monday, June 09, 2003 11:51 AM > To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > Subject: [cvsnt] Class File update > > > Team: > > I am trying to upload Java file and the corresponding class files into > WinCVS 1.3 > First time it works perfect and no issues at all. > > But if there are any changes to the Java file and if the changes are very > minimal - may be changes in the variable names, and I recompile it, I > could still update the new version of Java file. The class also turns red > but when I try to commit it, it doesn't update the new version into the > repository. > > Have this topic been discussed earlier? If so, lead me to the correct > topic title so that I can get more info. > > Thanks, > > Raj. > > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs