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/01/21 23:29:26 UTC

[jira] Moved: (SUREFIRE-240) need to enableassertions when running tests.

     [ http://jira.codehaus.org/browse/SUREFIRE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MSUREFIRE-32 to SUREFIRE-240:
------------------------------------------------

    Complexity:   (was: Novice)
           Key: SUREFIRE-240  (was: MSUREFIRE-32)
       Project: Maven Surefire  (was: Maven 2.x Surefire Plugin)

> need to enableassertions when running tests.
> --------------------------------------------
>
>                 Key: SUREFIRE-240
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-240
>             Project: Maven Surefire
>          Issue Type: Improvement
>         Environment: all
>            Reporter: Dave Sag
>         Assigned To: Jason van Zyl
>            Priority: Critical
>
> My code relied heavily on the java1.4 assert command and my unit tests explicitly test based on those assetions.
> but when i run m2 test the surefire plugin does not execute with the -enableassertions turned on, so my tests fail.
> looking in the documentation for the surefire plugin on http://maven.apache.org/maven2/plugins/maven-surefire-plugin/test-mojo.html I see no way of setting that flag.
> could it please be added.  this is areal blocker for me.
> dave

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