exclude tag is too powerful in a multi user environment

From: quig (quig_at_ai.mit.edu)
Date: 11/11/03 

Date: 11 Nov 2003 14:27:30 -0800

our project has a fileset for excluding files/dirs that are not ready
for others in our group to use. however, this causes problems for the
person working on those excluded files since they cannot forcefully
include them w/o removing them from the common fileset in the build
file. that could cause problems if checked in to CVS since the
not-ready code would cause problems for the other people. (confused?
i am.)

an example:

<fileset name="common.excludes">
  <exclude name="foo/bar/" />
  <exclude name="arc/tan/line/" />
  ...
</fileset>

<target...>
 <javac ....
   <include name="${subdir}**/*.java" />
   <patternset refid="${common.excludes}" />
 ....>
</target>

the problem happens when subdir is something in the path of one of the
common.excludes.

ie. subdir = arc/tan/

has anyone found a way to keep other people from building part of a
project, work on that part yourself, and not have concurrency problems
when someone checks in the build file that opens up broken code to
everyone?