Re: problem with <propertyfilelabelincrementer> and Ants <buildnumber> task causing perfect storm of label hell
Jeffrey Fredrick <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Cool, thanks for the patch! A bootstrapper could do that by pinging the jmx interface either via http or rmi, but it wouldn't take effect during the current build. OTOH did you know that the config.xml is already reloaded when a build request goes into the queue? So — unless your build has been queued behind a long build — the config.xml has probably just been checked and reloaded if needed anyways. Jtf -- Build engineering training: http://ci-guys.com/training.php On Mon, Mar 23, 2009 at 8:57 AM, David Corley <[email protected]> wrote: > Hey Jeffrey, > Documentation patch for configxml.html attached. > I've also created an issue in JIRA and attached the same documentation > patch. > http://jira.public.thoughtworks.org/browse/CC-900 > > Regards, > Dave > > P.S. I posted another question on the mailing lists regarding the interval > at which Cruisecontrol checks for updates to the config.xml it is using. > Is it technically possible with the current codebase to write a > bootstrapper that allows users to force a re-check of config.xml? ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Cruisecontrol-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user