maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <>
Subject [jira] Commented: (SUREFIRE-767) Support JUnit4 and the Java Security Manger
Date Thu, 08 Sep 2011 06:57:32 GMT


Kristian Rosenvold commented on SUREFIRE-767:

JUnit3 is capable of running without any kind of custom security policy or exceptions whatsover,
which means it's 100% realistic. The annotation processing in JUnit4 will require a specially
tuned security policy, and it will never be possible to get this environment to be "as clean"
as the JUnit3 version. But generally the architectural tuning that was applied to get security
policies working for junit3 should cover most of the grunt work needed to get this working
with JUnit4. 

I'm moving this straight to backlog but will certainly look at any patches with integration
tests that arrive, it's a cool first patch for someone to make (hint hint). I think there
were some samples on the linked junit3 issue 

> Support JUnit4 and the Java Security Manger
> -------------------------------------------
>                 Key: SUREFIRE-767
>                 URL:
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Junit 4.x support
>    Affects Versions: 2.9
>         Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500)
> Maven home: C:\Java\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_24\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Gary Gregory
> Surefire support JUnit3 but not JUnit 4 to run tests under the Java Security Manger.
Please add support for JUnit 4.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message