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 2006/04/30 00:52:19 UTC

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

     [ http://jira.codehaus.org/browse/SUREFIRE-35?page=all ]

Brett Porter updated SUREFIRE-35:
---------------------------------

    Fix Version: 2.0

> 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
>     Assignee: Jason van Zyl
>      Fix For: 2.0

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