You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2006/03/22 23:51:13 UTC

[jira] Updated: (MPTEST-43) Add the ability to control junit's showoutput attribute

     [ http://jira.codehaus.org/browse/MPTEST-43?page=all ]

Lukas Theussl updated MPTEST-43:
--------------------------------

    Fix Version: 1.8

> Add the ability to control junit's showoutput attribute
> -------------------------------------------------------
>
>          Key: MPTEST-43
>          URL: http://jira.codehaus.org/browse/MPTEST-43
>      Project: maven-test-plugin
>         Type: Improvement

>     Reporter: Matthias Kerkhoff
>      Fix For: 1.8

>
>
> There are situations in which the full output of the junit task is needed. 
> This happens typically when the test fails due to an internal error (as opposed to a test failure). For example, if you have a test case which doesn't have all required classes in its classpath, invoking this test will create a ClassNotFoundException. Other examples might include test cases which rely on the presence or execution of native code.
> The stack trace for junit errors that occur before the test method is executed will only be visible if the showoutput attribute of the junit task is set to true. 
> I would suggest to either make the showoutput attribute configurable through an additional maven property and/or to set showoutput=true unconditionally if maven is executed in debug mode (-X option).

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