You are viewing a plain text version of this content. The canonical link for it is here.

Posted to surefire-dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/04 14:28:14 UTC

[jira] Created: (SUREFIRE-35) refine use of assertion enablement

refine use of assertion enablement
----------------------------------

         Key: SUREFIRE-35
         URL: http://jira.codehaus.org/browse/SUREFIRE-35
     Project: surefire
        Type: Improvement

    Versions: 2.0    
    Reporter: Brett Porter
 Assigned to: Jason van Zyl 


Currently, the assertions are correctly enabled on the classloader when not forking. However, when forking, setting them on the classloader didn't work, so -ea is passed in to the forked process.

This is not harmful, though if there were assertions in the surefire provider or its dependencies (eg, testng), they would be checked unnecessarily.

-- 
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