]
Mickael Istria updated JBIDE-11301:
-----------------------------------
Fix Version/s: (was: 3.3.x)
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/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
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/jo...
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: