[jira] Updated: (MNG-3179) [regression] incorrect handling of build errors in the reactor
[ http://jira.codehaus.org/browse/MNG-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3179: --- Fix Version/s: (was: 2.1) 2.1-alpha-1 This along with general error reporting needs to be done before alpha-1. > [regression] incorrect handling of build errors in the reactor > -- > > Key: MNG-3179 > URL: http://jira.codehaus.org/browse/MNG-3179 > Project: Maven 2 > Issue Type: Bug > Components: Command Line, Reactor and workspace >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Assignee: Jason van Zyl >Priority: Minor > Fix For: 2.1-alpha-1 > > > example: introduce an error into the Maven trunk build (I removed the jdom > dependency from maven-model to cause compile failures), and run "mvn clean > install". > You get the error in the project, then the list of reactor projects with > success/fail/not built, then the errors again, then: > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] BUILD ERRORS > [INFO] > > [INFO] Total time: 6 seconds > [INFO] Finished at: Mon Sep 03 10:18:07 EST 2007 > [INFO] Final Memory: 20M/37M > [INFO] > > FATAL ERROR: Unable to configure the Maven application > For more information, run with the -e flag > I expect that: > * the build failures should only be output once in the --fail-fast mode > * it should be BUILD FAILURES, not BUILD ERRORS > * the FATAL ERROR message should not be present at the end -- 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] Updated: (MNG-3179) [regression] incorrect handling of build errors in the reactor
[ http://jira.codehaus.org/browse/MNG-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-3179: -- Fix Version/s: 2.1.x > [regression] incorrect handling of build errors in the reactor > -- > > Key: MNG-3179 > URL: http://jira.codehaus.org/browse/MNG-3179 > Project: Maven 2 > Issue Type: Bug > Components: Command Line, Reactor and workspace >Affects Versions: 2.1-alpha-1 >Reporter: Brett Porter >Priority: Minor > Fix For: 2.1.x > > > example: introduce an error into the Maven trunk build (I removed the jdom > dependency from maven-model to cause compile failures), and run "mvn clean > install". > You get the error in the project, then the list of reactor projects with > success/fail/not built, then the errors again, then: > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] BUILD ERRORS > [INFO] > > [INFO] Total time: 6 seconds > [INFO] Finished at: Mon Sep 03 10:18:07 EST 2007 > [INFO] Final Memory: 20M/37M > [INFO] > > FATAL ERROR: Unable to configure the Maven application > For more information, run with the -e flag > I expect that: > * the build failures should only be output once in the --fail-fast mode > * it should be BUILD FAILURES, not BUILD ERRORS > * the FATAL ERROR message should not be present at the end -- 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