[ http://jira.codehaus.org/browse/CONTINUUM-354?page=comments#action_53852 ]
Matthew Beermann commented on CONTINUUM-354: -------------------------------------------- No, CONTINUUM-330 didn't solve this. Here's why: 1. Add a new <module/> to the parent project and check in. 2. Rebuild the parent project. 3. I would expect the new module to be added to the Continuum project list, if it doesn't exist already. However, no such thing occurs. It seems that Continuum will check/add modules when the parent project is first added, but not when the parent project changes. It should, IMO. > Need a way to poll for new projects > ----------------------------------- > > Key: CONTINUUM-354 > URL: http://jira.codehaus.org/browse/CONTINUUM-354 > Project: Continuum > Type: Improvement > Versions: 1.0-beta-1 > Reporter: Matthew Beermann > Fix For: 1.1 > > > The feature where Continuum can populate its build list from a URL is > wonderful; it'd be even more wonderful if it could remember that URL and poll > it periodically. We have a "master build list" of all projects that we'll use > to initially populate the build database; but ideally we could simply add a > new project to that in CVS and have Continuum just pick it up. > This is a feature that we've (somewhat painfully) managed to implement in > CruiseControl, and it's a must-have if we're going to switch over... this > might or might not depend on CONTINUUM-330. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
