[ https://issues.apache.org/jira/browse/TAP5-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723210#comment-14723210 ] 

Hudson commented on TAP5-2494:
------------------------------

ABORTED: Integrated in tapestry-trunk-freestyle #1484 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/1484/])
TAP5-2494: CronSchedule can now be created with a specific TimeZone (jochen.kemnade: rev fb1d268257a9750b389cafe25e587194750d8af9)
* tapestry-ioc/src/main/java/org/apache/tapestry5/ioc/services/cron/CronSchedule.java


> CronSchedule timezone access
> ----------------------------
>
>                 Key: TAP5-2494
>                 URL: https://issues.apache.org/jira/browse/TAP5-2494
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.3.7, 5.4, 5.3.8
>            Reporter: Volker Lamp
>              Labels: easyfix, patch
>             Fix For: 5.4
>
>         Attachments: TAP5-2494.patch
>
>
> CronSchedule can be instantiated with a cron expression string, but there is no way to set a time zone. Specifically, the cron expression is not expected to contain time zone information; there is neither a CronSchedule constructor with a TimeZone argument nor with a CronExpression argument; and CronSchedule's CronExpression field is private.
> The proposed solution is to add a constructor that will accept a TimeZone argument. The existing one-argument constructor would set the default time zone.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)