SCM: Where Java Files Go

At work, our team of ten developers is in the pre-stages of implementing a Software Configuration Management tool, namely Visual Source Safe. Yes, that's right. Ten developers. And we don't have an SCM tool. Do not get me started. Point is, after a long struggle, we probably are going to get VSS. We just have to show we already know how to use it.

We are pretty much in agreement about what belongs in VSS. In addition to a project for the intranet code, custom tags, and CFCs, we've decided to create an /assets project at the root to store Web assets that are not part of a deployment, but are essential to a project. This includes any graphics files in their native format (.psd, .png, whatever) and, if we were to use them, .fla files.

As a ColdFusion shop, we don't do "real" programming (of course we do, I'm just saying that) in that we don't have source code files that are compiled and then the compiled files deployed. We deploy code that includes markup (.cfm) and processing (.cfc).

In shops that use other environments, I assume that .java files are included in VSS (or CVS for open sourcers), and when compiled, the resulting .class files are deployed. There isn't much need to keep the compiled .class files in an SCM, is there?