1. Maven
  2. MNG-4782

Automatically dump stack trace in case of internal Maven error


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.0-beta-2
    • Fix Version/s: 3.0-beta-3
    • Component/s: Errors
    • Labels:


      This output isn't really helpful:

      [ERROR] Internal error: java.lang.NullPointerException -> [Help 1]
      [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] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1]

      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.


        Benjamin Bentmann created issue -
        Benjamin Bentmann made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Benjamin Bentmann [ bentmann ]
        Fix Version/s 3.0-beta-3 [ 16681 ]
        Resolution Fixed [ 1 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
        Mark Thomas made changes -
        Workflow jira [ 12715057 ] Default workflow, editable Closed status [ 12754633 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
        Mark Thomas made changes -
        Workflow jira [ 12951401 ] Default workflow, editable Closed status [ 12987694 ]


          • Assignee:
            Benjamin Bentmann
            Benjamin Bentmann
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: