On Mon, Jul 17, 2000 at 04:24:58PM -0700, Eric Chamberlain wrote:
> That doesn't seem like a reasonable answer. CVS should be able to handle
> the intermediate files just fine. I can certainly imagine scenarios in which
> one would want to put up sections of pre-compiled slowly-changing chunks of
> code (for efficiency reasons).
If you need efficiency, you use your build system to not regenerate those
files every time you do a build. Only when the base source changes!
> Is there a *Java-related* reason not to put .class and .jar files up in CVS?
Not a java related reason. Just a basic standard good programming and
configuration management reason, that is independent of the language being
used.
Would you check in object or library files into CVS? No (unless that's the
only way you have them). So the same goes for .class and .jar files. It's
just damned poor design.
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
