Organizing *-custom.xml and *-deploy.properties

In all of the Keel documentation/tutorials that I've seen, all of the deployment customizations take place in files within the keel-build project. However, as my group builds apps and services, we'd like to be able store the *-custom.xml and *-deploy.properties files in CVS without having to maintain a copy all of the other common stuff in keel-build. Is there another way to organize such that the custom deployment configurations exists outside of keel-build? It looks like the location of the dprop directory is hard-coded. 

- Justin

--
ThatOne Company
http://www.thatone.com/