So far I've been concentrating on getting my source code from cvs repository into VAJ using vaj2cvs. Recently I've had to patch a 3rd-party class library in a somewhat unorthodox way. This caused code to break when other users updated the code that was dependent on the patch. Their only option was to apply the same patch manually.
This seems like a good place for cvs. If I maintained my 3rd-party class libraries in cvs then the other developers would only have to update the appropriate projects to become up to date with any patches or version changes. My question is, does vaj2cvs support the importation of class files from cvs? Or does it only import source files?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So far I've been concentrating on getting my source code from cvs repository into VAJ using vaj2cvs. Recently I've had to patch a 3rd-party class library in a somewhat unorthodox way. This caused code to break when other users updated the code that was dependent on the patch. Their only option was to apply the same patch manually.
This seems like a good place for cvs. If I maintained my 3rd-party class libraries in cvs then the other developers would only have to update the appropriate projects to become up to date with any patches or version changes. My question is, does vaj2cvs support the importation of class files from cvs? Or does it only import source files?
Hello;
This works like a dream... I use it to keep all of the JDBC Drivers (commercial is always .class files) up to date, and it just keeps working.
-Eric.