adding a new schedule does not work on first activation
-------------------------------------------------------
Key: CONTINUUM-2195
URL: http://jira.codehaus.org/browse/CONTINUUM-2195
Project: Continuum
Issue Type: Bug
Components: Core system
Affects Versions: 1.4.0
Reporter: Brett Porter
When the schedule was first created (with no projects assigned), it was
"activated". However, after assigning a project to it, it did not fire. Editing
the schedule (no changes made), caused it to fire on the assigned project. The
log is as follows:
{code}
2009-04-22 20:03:51,005 [btpool0-1] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator -
Activating schedule minutely
2009-04-22 20:37:13,488 [btpool0-7] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator -
Deactivating schedule minutely
2009-04-22 20:37:13,488 [btpool0-7] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator - Stopping
active schedule "minutely".
2009-04-22 20:37:13,488 [btpool0-7] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator -
Activating schedule minutely
2009-04-22 20:37:13,494 [btpool0-7] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator -
minutely: next fire time ->Wed Apr 22 20:38:00 EST 2009
2009-04-22 20:38:00,019 [continuumScheduler_Worker-4] INFO
org.apache.maven.continuum.build.settings.DefaultSchedulesActivator -
>>>>>>>>>>>>>>>>>>>>> Executing build job (minutely)...
{code}
--
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
