[jira] Commented: (MSUREFIRE-137) failure reason not displayed
[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=comments#action_67424 ] Carlos Sanchez commented on MSUREFIRE-137: -- give a try to the surefire-report plugin > failure reason not displayed > > > Key: MSUREFIRE-137 > URL: http://jira.codehaus.org/browse/MSUREFIRE-137 > Project: Maven 2.x Surefire Plugin > Type: Improvement > Versions: 2.2 > Reporter: Jörg Hohwiller > Assignee: Carlos Sanchez > > > Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit > test fails. > Of course I can run the test within my IDE but in my case it worked within > the IDE and only did NOT work in maven2. > After times of digging I found that there is a bug in sufrefire > (MSUREFIRE-115) causing this problem. > It would have saved me a lot of time if surefire would log the reason if a > test fails. This should include stacktraces of Exceptions if started with -X. > Currently I only get: > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failure. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403) > what is absolutely useless to track down the problem. -- 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
[jira] Commented: (MSUREFIRE-137) failure reason not displayed
[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=comments#action_67373 ] Jörg Hohwiller commented on MSUREFIRE-137: -- I can think of two things: 1. surefire.useFile=false is default, -Dsurefire.useFile=true needs to be activated 2. if "surefire.useFile=false" and one or more test fails, a single line is printed telling where to find the detailled reports. Anyways from my point of view this issue can be closed. I just wanted to point this out from the "outside users view". Some users maybe have no clue about what maven is and do not want to spend their time on it - their only intention might be to fix a problem as quickly as possible (e.g. to get an open-source project build that is maintained with maven). > failure reason not displayed > > > Key: MSUREFIRE-137 > URL: http://jira.codehaus.org/browse/MSUREFIRE-137 > Project: Maven 2.x Surefire Plugin > Type: Improvement > Versions: 2.2 > Reporter: Jörg Hohwiller > Assignee: Carlos Sanchez > > > Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit > test fails. > Of course I can run the test within my IDE but in my case it worked within > the IDE and only did NOT work in maven2. > After times of digging I found that there is a bug in sufrefire > (MSUREFIRE-115) causing this problem. > It would have saved me a lot of time if surefire would log the reason if a > test fails. This should include stacktraces of Exceptions if started with -X. > Currently I only get: > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failure. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403) > what is absolutely useless to track down the problem. -- 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
[jira] Commented: (MSUREFIRE-137) failure reason not displayed
[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=comments#action_67357 ] Carlos Sanchez commented on MSUREFIRE-137: -- all are at http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html printing all those will make the output pretty complicated > failure reason not displayed > > > Key: MSUREFIRE-137 > URL: http://jira.codehaus.org/browse/MSUREFIRE-137 > Project: Maven 2.x Surefire Plugin > Type: Improvement > Versions: 2.2 > Reporter: Jörg Hohwiller > Assignee: Carlos Sanchez > > > Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit > test fails. > Of course I can run the test within my IDE but in my case it worked within > the IDE and only did NOT work in maven2. > After times of digging I found that there is a bug in sufrefire > (MSUREFIRE-115) causing this problem. > It would have saved me a lot of time if surefire would log the reason if a > test fails. This should include stacktraces of Exceptions if started with -X. > Currently I only get: > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failure. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403) > what is absolutely useless to track down the problem. -- 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
[jira] Commented: (MSUREFIRE-137) failure reason not displayed
[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=comments#action_67354 ] Jörg Hohwiller commented on MSUREFIRE-137: -- I also found the reports unter target/surefire-reports in the meantime. Thanks for the hint above to. But why not just printing out this hint(s) by default (e.g. eclipse:eclipse suggest me to use -DdownloadSources=true). Maybe I am stupid. But surely I am not the only one. So why don't you think about making you life easier and getting less issues like this one ;) > failure reason not displayed > > > Key: MSUREFIRE-137 > URL: http://jira.codehaus.org/browse/MSUREFIRE-137 > Project: Maven 2.x Surefire Plugin > Type: Improvement > Versions: 2.2 > Reporter: Jörg Hohwiller > Assignee: Carlos Sanchez > > > Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit > test fails. > Of course I can run the test within my IDE but in my case it worked within > the IDE and only did NOT work in maven2. > After times of digging I found that there is a bug in sufrefire > (MSUREFIRE-115) causing this problem. > It would have saved me a lot of time if surefire would log the reason if a > test fails. This should include stacktraces of Exceptions if started with -X. > Currently I only get: > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failure. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403) > what is absolutely useless to track down the problem. -- 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
[jira] Commented: (MSUREFIRE-137) failure reason not displayed
[ http://jira.codehaus.org/browse/MSUREFIRE-137?page=comments#action_67347 ] Olivier Lamy commented on MSUREFIRE-137: Try with adding -Dsurefire.useFile=false. And certainly close this issue :-) > failure reason not displayed > > > Key: MSUREFIRE-137 > URL: http://jira.codehaus.org/browse/MSUREFIRE-137 > Project: Maven 2.x Surefire Plugin > Type: Improvement > Versions: 2.2 > Reporter: Jörg Hohwiller > > > Neigther with "mvn test" nor with "mvn -X test" I get the reason why a unit > test fails. > Of course I can run the test within my IDE but in my case it worked within > the IDE and only did NOT work in maven2. > After times of digging I found that there is a bug in sufrefire > (MSUREFIRE-115) causing this problem. > It would have saved me a lot of time if surefire would log the reason if a > test fails. This should include stacktraces of Exceptions if started with -X. > Currently I only get: > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failure. > at > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugn.java:403) > what is absolutely useless to track down the problem. -- 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
