>-----Original Message----- >From: Kirk Woll [mailto:[EMAIL PROTECTED]] >Perhaps, but if I were you I would seriously reconsider having unknown >(unnecessary) class files in your output directory. Couldn't you put >those other class files in a different directory?
They aren't unknown, they just got their either by me building with something else (like make) or by me building with a different project. For example, I might be doing some work on the client, so I use my "client" project. But then I want to do some work with the installer so I switch to my "installer" project. The installer project most likely uses classes from the "client" project. I don't think one should assume that source and output directories are "exclusive" to a project. > > Also, our build does a good amount of code generation, where java >files are > > generated and compiled. > >Really? How is maintaining that working out? We generate the code as part of the build, so there really isn't any extra maintenance. But the time involved in doing this generation and compilation is part of the reason I like to suck class files off of the build machine instead of having to build the entire tree myself. -Tom _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
