A better solution is to switch from DTD entities to the CCNET 1.4's preprocessor include mechanism (described in your link). It watches for changes in ccnet.config and any included file (even deeply nested includes).
On Oct 10, 3:44 am, Andrei Paleyes <[EMAIL PROTECTED]> wrote: > If you have not only one ccnet.config file but some more files > included e.g. by <!ENTITY referencedFile.xml> references, then make > sure that you've modified ccnet.config file. The problem is that > Cruise Control.NET cannot detect changes in configuration if it's main > configuration file, ccnet.config, wasn't modified. Here is the link > were this problem was described in few words (see "Configuration file > processing" > section):http://confluence.public.thoughtworks.org/display/CCNET/CCNet+1.4+Rel... > For our project we've solved this problem just by adding comment in > ccnet.config > > <!-- > For CC.NET to reload configuration ccnet.config file has to be > modified. > Increment the following counter to indicate that configuration update > is required. > Modification: #xx. > --> > > and increasing xx every time we've made changes in referenced files. > > On Oct 6, 4:03 pm, Alex <[EMAIL PROTECTED]> wrote: > > > > > I am in the process of putting all my configs in source control, and > > although in principle it is working, the service never recognizes the > > new file. It is valid XML, because if I bounce the service it picks up > > the changes no problem. However, the service will not do see the > > changes on it's own. Anyone have any luck getting this working before?- > > Hide quoted text - > > - Show quoted text -
