It seems to me that in your case, as well as in many others, it will be much better to have certain folders just excluded from project path. Excluded folers are not scanned on project loading, they are ignored by compilation/build process, etc. If you think that better project path management will help in your case, please say so here - I suggested this feature recently and if there is enough support it may actually be implemented soon to our mutual satisfaction ;-)
Alex. "Walter Mundt" <[EMAIL PROTECTED]> writes: > I'd really like to exclude files in my build tree (build/ under the project > root) from being opened in the ctrl-N dialog. Having a configurable list of > (recursively) excluded directories would be best. > > We use a custom in-house layout for the files in development, and then copy > all jsp, xml, and other configuration files into a deployment structure in > build. So, for any file, there are always (at least) two copies, one of > which is to be edited, and one of which is not. So I don't want the copy > that will be overwritten showing up in the ctrl-N dialog. > > Thanks, > -Walter Mundt _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
