Deal with case sensitivity of class names

[jmaessen]

If we have top-level bindings for, say, empty and Empty, we end up with classes whose names collide on a case-insensitive file system (such as OS X).

Probably best to deal with this short-term by generating jar files. Put all classes from a component into a single jar. Use wildcards in the classpath to permit all jars in cache to be loaded. See  http://java.sun.com/javase/6/docs/technotes/tools/windows/classpath.html for more info on path wildcards. We still need to worry about case collisions among component names, but this is much less of a concern I suspect.

Meanwhile I'm working around this in the sole case where I've run into the problem so far.