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

ASF GitHub Bot commented on NIFI-2688:
--------------------------------------

GitHub user alopresto opened a pull request:

    https://github.com/apache/nifi/pull/974

    NIFI-2688 Resolved failing unit test for European/Australian time zones

    Please test on a variety of systems with worldwide timezones and 
non-standard locale date formats. 

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

    $ git pull https://github.com/alopresto/nifi NIFI-2688

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

    https://github.com/apache/nifi/pull/974.patch

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

    This closes #974
    
----
commit e1598cc3a4ecd2019af6cc8e53b05d88715e01e4
Author: Andy LoPresto <alopre...@apache.org>
Date:   2016-08-31T03:14:34Z

    NIFI-2688 Added test for varying date format assertions.

commit cdfb7229a19d2617a07038fad3f6b07b3fbee070
Author: Andy LoPresto <alopre...@apache.org>
Date:   2016-08-31T03:46:33Z

    NIFI-2688 Fixed regex pattern for all timezones using standard locale date 
time format.

----


> ConfigEncryptionToolTest causes build to fail when building using 4 letter 
> time locales (e.g. AEST)
> ---------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2688
>                 URL: https://issues.apache.org/jira/browse/NIFI-2688
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Tools and Build
>    Affects Versions: 1.0.0
>            Reporter: Andre
>            Assignee: Andy LoPresto
>            Priority: Trivial
>              Labels: internationalization, test, timezone
>             Fix For: 1.1.0
>
>
> ConfigEncryptionToolTest causes build to fail when using 4 letter timezones.



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

Reply via email to