Since CVS doesn't store binary diffs, storing all of the jars in CVS could chew up disk space quickly if you're going to be changing versions of Cocoon often.
It could also make it painful to upgrade to a new version of Cocoon later. You could consider storing the Cocoon war, either in CVS or as a Maven project, and using some automation to extract that war into your development and/or build environment. Like everything, this approach comes with its own disadvantages. Regarding CVS, you should be able to check in a directory with mixed binary and text files. There's a file you can edit in the CVSROOT (can't remember which file) that lets you configure CVS to recognize which files are binary by their extension. Morley > -----Original Message----- > From: Justin Fagnani-Bell [mailto:[EMAIL PROTECTED] > Sent: Tuesday December 16, 2003 7:43 PM > To: [EMAIL PROTECTED] > Subject: Re: OT: How do you use CVS? > > I guess I'm asking if it's a bad idea to store all 30+ MBs of JAR files > in CVS. I don't really have control over their revisions, but I guess > making a release with certain JARs is the point, right? And in some > directories I have a mixture of text files and binaries, so I won't be > able to check in the whole directory, I'll have to check in each file > individually. > > -Justin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
