Hi, all, I've noticed that in many places in Geronimo repository the files and subdirectories generated by build scripts are put to svn:ignore properties of the corresponding directories, so that they do not get in the way when checking a working copy status and preparing a patch/commit.
However in some other (newer?) places the build-generated files and subdirectories are not being added to svn:ignore properties. I think that it worths to have a consistent policy in this matter. Personally, I think that it makes sense to add all the known build-generated files and directories to the corresponding local svn:ignore, as svn:ignore idea is to mark the files and directories that are not going to be committed to repository. So if our build generates something somewhere and we know that it generates that, and we know we're not going to commit that (like 'build', 'target' directories, log files etc.) - let's mark it so. On the other hand, one can configure his own ~/.subversion/config [global-ignores] property to ignore some file patterns throughout the whole repository. However, this approach is good for some personal settings, and it has its disadvantages: first, it's needed to be done by each developer; second, it creates a risk of hiding some important files being hidden by some global wildcard; third, it's a global-only setting that can't go into details of particular build parts. Using local svn:ignore properties looks preferable as it only covers the particular files in particular directory. What would you people say? There's an issue created with proposed patches on this issue, it's http://issues.apache.org/jira/browse/GERONIMO-3957. Also, this issue already had some intensive discussions since a year ago, please check them also: http://thread.gmane.org/gmane.comp.java.geronimo.devel/44831 http://thread.gmane.org/gmane.comp.java.geronimo.devel/47357 http://thread.gmane.org/gmane.comp.java.geronimo.devel/61416 Thanks! Vasily
