[jbosstools-issues] [JBoss JIRA] (JBIDE-11301) no stacktrace when junit tests fail

[Alexey Kazakov (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12814356#comment-12814356 ] 

Alexey Kazakov commented on JBIDE-11301:
----------------------------------------

[~maxandersen], I'm OK with the current situation.
When you run a bunch of test plugins (an entire component for example) then the output is so long that you it's more convenient to see the particular surefire-report files rather than scrolling the console.
When you run a single plugin it would be faster/easier to get stacktraces in console output. But we can go to the corresponding surefire-report files. Not a big deal.
                
> no stacktrace when junit tests fail
> -----------------------------------
>
>                 Key: JBIDE-11301
>                 URL: https://issues.jboss.org/browse/JBIDE-11301
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, upstream
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Alexey Kazakov
>            Assignee: Mickael Istria
>            Priority: Minor
>             Fix For: LATER
>
>
> If I run JBT tycho build locally for trunk, for example:
> mvn clean install -fae -e -P default -f cdi/tests/pom.xml
> and there is some test failures then I don't see any stacktrace in console. Just a text message from the JUnit test assert.
> -Dsurefire.useFile=false does not help.
> But I see the stacktrace in <target>/surefire-reports
> In Beta1 branch it works fine.
> I don't see stacktrace in console output in Hudson either but I'm not sure it's a problem there.
> For example https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--cdi/lastCompletedBuild/console
> But for local builds it's very useful to see the full stacktrace in console.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira