[
http://jira.codehaus.org/browse/MNG-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4782.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0-beta-3
Assignee: Benjamin Bentmann
Done in [r989869|http://svn.apache.org/viewvc?view=revision&revision=989869].
> Automatically dump stack trace in case of internal Maven error
> --------------------------------------------------------------
>
> Key: MNG-4782
> URL: http://jira.codehaus.org/browse/MNG-4782
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Errors
> Affects Versions: 3.0-beta-2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Trivial
> Fix For: 3.0-beta-3
>
>
> This output isn't really helpful:
> {noformat}
> [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
> {noformat}
> We know by the nature of this exception that we need more information to
> analyze the issue (where did the nested exception occur within the core?),
> i.e. the stack trace is pretty much required. As such, we should
> automatically dump it to the console as if {{-e}} was given. This is not only
> more convenient for the user as it saves him from re-running the build but
> also ensures we capture valuable data for an error that might only show up
> occasionally.
--
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
