[
https://issues.jboss.org/browse/ARQ-690?page=com.atlassian.jira.plugin.sy...
]
Ondrej Zizka edited comment on ARQ-690 at 2/14/12 5:12 AM:
-----------------------------------------------------------
What's left to do: Add {{-Djava.security.debug}}
See
http://docs.oracle.com/javase/1.5.0/docs/guide/plugin/developer_guide/deb...
{code}
-Djava.security.manager -Djava.security.policy==xxx.policy
-Djava.security.debug=access,failure
{code}
To ignore the JDK's default policy which merges with the specified as default
behavior, the policy path is prepended with '='.
was (Author: ozizka):
What's left to do: Add {{-Djava.security.debug}}
See
http://docs.oracle.com/javase/1.5.0/docs/guide/plugin/developer_guide/deb...
{code}
-Djava.security.manager -Djava.security.policy==xxx.policy
-Djava.security.debug=access,failure
{code}
Verify ability to run under a security manager (evt. create a policy
file)
--------------------------------------------------------------------------
Key: ARQ-690
URL:
https://issues.jboss.org/browse/ARQ-690
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Base Implementation, JBoss Containers
Affects Versions: 1.0.0.CR6
Reporter: Ondrej Zizka
Assignee: Aslak Knutsen
Verify whether Arquillian is able to run under security manager.
Presumably, we need to create a security policy file for arquillian.
Test with JBoss AS7 testsuite, using -Dsecurity.manager [ -Dsecurity.policy=<path>]
- see
https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use... .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira