> You might want to rethink this concept of getting rid of "unnecessary" files.
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? > Also, our build does a good amount of code generation, where java files are > generated and compiled. Really? How is maintaining that working out? Kirk Tom Wagner wrote: >We have a large source tree. I usually make projects that are rooted at a >small part of that source tree. > >So my source root might be net/comanage/foo and my project root is >net/comanage/foo/install. If I tell my project to do a dependency based >make, the first thing it does is delete all the class files in the output >directory for things that aren't in the project. This Is Bad. > >Also, our build does a good amount of code generation, where java files are >generated and compiled. I fear that even if I set my project root to be the >root of the source tree, if I copied over the class files from a build >machine, Idea would then blow away all the class files that go with >generated files. > >You might want to rethink this concept of getting rid of "unnecessary" >files. > >-Tom >-- >[EMAIL PROTECTED] >"But we don't talk about it > we just become shadows of ourselves" > -Duncan Sheik, In the Absence of Sun > >_______________________________________________ >Eap-list mailing list >[EMAIL PROTECTED] >http://www.intellij.com/mailman/listinfo/eap-list > > _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
