camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9938) TimerPatternConverter - Should be more strict
Date Mon, 23 May 2016 09:40:13 GMT


ASF GitHub Bot commented on CAMEL-9938:

GitHub user anoordover opened a pull request:


    We support the following convention (case insensitive):
    - only numbers
    - (number)h, (number)hour or (number)hours to define hours;
    - (number)m, (number)min, (number)minute, (number)minutes to define minutes;
    - (number)s, (number)sec, (number)second, (number)seconds to define seconds.
    You are only allowed to define each of hours, minutes and seconds once.
    After replacing the first occurrence of hours, minutes and seconds and passing the previous
check the length of the resulting string is checked for any remaining characters.

You can merge this pull request into a Git repository by running:

    $ git pull CAMEL-9938TimePattern

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #994
commit fad1d291f8d15dabaae21382773bb0b5b86f7b68
Author: Arno Noordover <>
Date:   2016-05-23T09:31:59Z



> TimerPatternConverter - Should be more strict
> ---------------------------------------------
>                 Key: CAMEL-9938
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.17.0
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.18.0
> So it would report an error if attempting to use 
> delay=5ssegegegegqergerg
> eg as today its too lenient and assume people do not make typo's. So if you type 5s then
its 5 seconds.

This message was sent by Atlassian JIRA

View raw message