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

Justin,

> 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. 

For the last round of build changes, I made some improvements in this area but
haven't had time to finish it off.  *-custom.xml already supports this, just
put the fully qualified path in your deploy.properties file. Please submit a
report on the SF tracker for the *-deploy.properties, and when I have some
time after 2.1 I'll look into this.

Shash