Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Cannot Reproduce
-
Affects Version/s: 1.8
-
Fix Version/s: 1.8.1
-
Labels:None
-
Environment:Build/running Apache AXIS2 testcase with maven 1.1.3
Description
I added the following 2 maven properties to"project.properties" file under axis2/modules/kernel/ directory. and do not see any securitty related logging information in the trace file. Similarly, the second part of the maven.junit.jvmargs, which is the specific policy file, mytestpolicy.policy, is also not loaded to the JVM.
------------------------------------------
maven.junit.fork=true
maven.junit.jvmargs=-Djava.security.debug=all -Djava.security.policy=c:/temp/mytestpolicy.policy
------------------------------------------
To reproducing this problem is quite simple and straight forward.
You can just use a simple testcase (any testcase is fine and no need to have any security codes) from your own; Add the 2 above properties to the project.properties file. then run the maven with your test.
Usually, if you see the log contains the "SCL" keywords, the security debug is being picked and used. otherwise, it is not.
Security log output example:
--------------------------------------
scl: (Thread[main,5,main]) getPermissions ProtectionDomain (file:/C:/Documents%20and%20Settings/mingcheu/ <no signer certificates>)
sun.misc.Launcher$AppClassLoader@24062406
<no principals>
java.security.Permissions@7da47da4 (
(java.lang.RuntimePermission exitVM)
(java.io.FilePermission \C:\Documents and Settings\mingcheu- read)
)
scl: (Thread[main,5,main])
I do see the security output. Please provide more information about your environment if it is still a problem.