You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/02/23 08:06:40 UTC
[jira] Updated: (SUREFIRE-34) Using security manager in a fork mode
causes an AccessControlException
[ http://jira.codehaus.org/browse/SUREFIRE-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated SUREFIRE-34:
---------------------------------
Fix Version/s: (was: 2.3)
2.4
> Using security manager in a fork mode causes an AccessControlException
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-34
> URL: http://jira.codehaus.org/browse/SUREFIRE-34
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 1.5.3 (2.1.3 plugin)
> Reporter: Vincent Siveton
> Priority: Critical
> Fix For: 2.4
>
> Attachments: SUREFIRE-34.diff
>
>
> Using securityManager in a forkmode causes java.security.AccessControlException in the createClassLoader() method
> Same things with setSystemProperties()
> Example:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkMode>pertest</forkMode>
> <argLine>-Djava.security.manager</argLine>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira