You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Roman S. Bushmanov (JIRA)" <ji...@apache.org> on 2007/06/26 13:06:26 UTC
[jira] Created: (HARMONY-4284) [buildtest][functional]
Misconfiguration in two functional tests
[buildtest][functional] Misconfiguration in two functional tests
-----------------------------------------------------------------
Key: HARMONY-4284
URL: https://issues.apache.org/jira/browse/HARMONY-4284
Project: Harmony
Issue Type: Bug
Components: build - test - ci
Reporter: Roman S. Bushmanov
Two functional tests
functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_02/F_SecureRandomTest_02.xml
functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_04/F_SecureRandomTest_04.xml
specify -Djava.security.policy==<policy file> command line option in their run configuration. This option (with double equals) forces runtime to ignore the default policy file.
The tests work with security providers but BC provider which is used by harmony as default crypto provider requires certain permissions to be granted to its codebase. The corresponding statement is located in the default policy.file which is ignored in the current run configuration of mentioned tests.
The patch fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-4284) [buildtest][functional]
Misconfiguration in two functional tests
Posted by "Vladimir Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ivanov resolved HARMONY-4284.
--------------------------------------
Resolution: Fixed
Thanks. Your patch was applied at 551020. Please, verify.
> [buildtest][functional] Misconfiguration in two functional tests
> -----------------------------------------------------------------
>
> Key: HARMONY-4284
> URL: https://issues.apache.org/jira/browse/HARMONY-4284
> Project: Harmony
> Issue Type: Bug
> Components: build - test - ci
> Reporter: Roman S. Bushmanov
> Assignee: Vladimir Ivanov
> Attachments: 4284.patch
>
>
> Two functional tests
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_02/F_SecureRandomTest_02.xml
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_04/F_SecureRandomTest_04.xml
> specify -Djava.security.policy==<policy file> command line option in their run configuration. This option (with double equals) forces runtime to ignore the default policy file.
> The tests work with security providers but BC provider which is used by harmony as default crypto provider requires certain permissions to be granted to its codebase. The corresponding statement is located in the default policy.file which is ignored in the current run configuration of mentioned tests.
> The patch fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-4284) [buildtest][functional]
Misconfiguration in two functional tests
Posted by "Vladimir Ivanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ivanov reassigned HARMONY-4284:
----------------------------------------
Assignee: Vladimir Ivanov
> [buildtest][functional] Misconfiguration in two functional tests
> -----------------------------------------------------------------
>
> Key: HARMONY-4284
> URL: https://issues.apache.org/jira/browse/HARMONY-4284
> Project: Harmony
> Issue Type: Bug
> Components: build - test - ci
> Reporter: Roman S. Bushmanov
> Assignee: Vladimir Ivanov
> Attachments: 4284.patch
>
>
> Two functional tests
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_02/F_SecureRandomTest_02.xml
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_04/F_SecureRandomTest_04.xml
> specify -Djava.security.policy==<policy file> command line option in their run configuration. This option (with double equals) forces runtime to ignore the default policy file.
> The tests work with security providers but BC provider which is used by harmony as default crypto provider requires certain permissions to be granted to its codebase. The corresponding statement is located in the default policy.file which is ignored in the current run configuration of mentioned tests.
> The patch fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4284) [buildtest][functional]
Misconfiguration in two functional tests
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman S. Bushmanov updated HARMONY-4284:
----------------------------------------
Attachment: 4284.patch
> [buildtest][functional] Misconfiguration in two functional tests
> -----------------------------------------------------------------
>
> Key: HARMONY-4284
> URL: https://issues.apache.org/jira/browse/HARMONY-4284
> Project: Harmony
> Issue Type: Bug
> Components: build - test - ci
> Reporter: Roman S. Bushmanov
> Attachments: 4284.patch
>
>
> Two functional tests
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_02/F_SecureRandomTest_02.xml
> functional/org/apache/harmony/test/func/api/java/security/F_SecureRandomTest_04/F_SecureRandomTest_04.xml
> specify -Djava.security.policy==<policy file> command line option in their run configuration. This option (with double equals) forces runtime to ignore the default policy file.
> The tests work with security providers but BC provider which is used by harmony as default crypto provider requires certain permissions to be granted to its codebase. The corresponding statement is located in the default policy.file which is ignored in the current run configuration of mentioned tests.
> The patch fixes the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.