maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maria Odea Ching (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRM-436) incorrect default cron expression for snapshots repository
Date Tue, 14 Aug 2007 02:08:47 GMT

    [ http://jira.codehaus.org/browse/MRM-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104778
] 

Maria Odea Ching commented on MRM-436:
--------------------------------------

Assuming that I don't have archiva.xml in ~/.m2/, so the one in $ARCHIVA_BASE$/conf/ (which
initially just contains an empty <configuration/>) is used..

The default-archiva.xml has '0 0,30 0 * * ?' as the default cron expression for the snapshots
repository. But it becomes '0 0' when displayed in the repositories page in archiva-webapp.
When I updated the snapshots repository config and set the cron expression to '0 0,30 0 *
* ?', I saw that there became two cron expression entries in its configuration in archiva.xml
<refreshCronExpression>0 0</refreshCronExpression> and <refreshCronExpression>30
0 * * ?</refreshCronExpression>.  Although this is the case, the cron expression displayed
in the webapp is still corrent, which is '0 0,30 0 * * ?'.

I suspect that the RegistryReader and RegistryWriter handles it as a special case when a ','
(comma) is recognized. 

There are two ways to approach this:
1. Set the default expression for the snapshots repo to be the same as for the releases
2. Set 2 <refreshCronExpression> values in default-archiva.xml for the snapshots repository
<refreshCronExpression>0 0</refreshCronExpression>  and <refreshCronExpression>30
0 * * ?</refreshCronExpression>.

I'll do the first one for now as this was what has been suggested above :)



> incorrect default cron expression for snapshots repository
> ----------------------------------------------------------
>
>                 Key: MRM-436
>                 URL: http://jira.codehaus.org/browse/MRM-436
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0-beta-1
>            Reporter: Brett Porter
>            Assignee: Maria Odea Ching
>             Fix For: 1.0-beta-2
>
>
> it is '0 0' which is not a valid value - it should probably be the same as for releases

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

        

Mime
View raw message