[
http://jira.codehaus.org/browse/MNG-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-2637.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: 3.x (to be reviewed))
Maven 3 now prints a reactor summary showing what the failure module was,
followed by the error report. IT also handles plugin loading better just in
time for this specific error.
> Logs improvment when using sub-projects
> ---------------------------------------
>
> Key: MNG-2637
> URL: http://jira.codehaus.org/browse/MNG-2637
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies, Logging
> Reporter: Emmanuel Lécharny
> Priority: Critical
> Attachments: maven-stack.txt
>
>
> When compiling a hierarchy of projects, and if something went wrong, like a
> missing plugin, there is absolutly now way to know, without grep through many
> pom.xml, which pom.xml is incorrect.
> It would be much more than cool to have a simple line like :
> [INFO] Getting plugins needed by project <path>/<project name>
> or
> [INFO] Getting dependency <depency-name><version> from repo <repository path>
> for project <path><project name>
> instead of a flood of line which makes no sense for the mere mortal ;)
--
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
