[jira] [Comment Edited] (CRYPTO-52) Improve assertion message when test fails due to lack of JCE Unlimited Strength Jurisdiction Policy Files.

["Chris Nauroth (JIRA)" <ji...@apache.org>]

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

Chris Nauroth edited comment on CRYPTO-52 at 5/4/16 7:04 PM:
-------------------------------------------------------------

Sorry... I think I'm completely missing a point about test fix process expectations.  I await clarification.  :-)  Are you saying this qualifies as a trivial change, as described here?

https://github.com/apache/commons-crypto/blob/master/CONTRIBUTING.md


was (Author: cnauroth):
Sorry... I think I'm completely missing a point about test fix process expectations.  I await clarification.  :-)  Are you saying this qualifies as a trivial change, as describe here?

https://github.com/apache/commons-crypto/blob/master/CONTRIBUTING.md

> Improve assertion message when test fails due to lack of JCE Unlimited Strength Jurisdiction Policy Files.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CRYPTO-52
>                 URL: https://issues.apache.org/jira/browse/CRYPTO-52
>             Project: Commons Crypto
>          Issue Type: Improvement
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: CRYPTO-52.001.patch
>
>
> {{JceCipherTest}} requires support for an AES key length of 256.  This is only available if the runtime JDK has installed the JCE Unlimited Strength Jurisdiction Policy Files.  When the test fails, the reason isn't clear.  We can improve this by detecting the maximum allowed key length and showing a more descriptive assertion message.



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