I'd planned to summarise what I did here tomorrow as its late... I very carefully audited every exception in the codebase and ensured that the message of each exception always captured any appropriate message from the cause. There are no more "shoulder shrugs".
The root simply duplicated all of these (which looked silly), and is easily obtained by the trace as you mention (with -e, not -X). If you want to restore and: a) you guarantee it doesn't duplicate the original message (which it did even before I did the above audit) b) that it actually gets the root cause (f.e., the root cause of ArtifactResolutionException was coming back as "Could not get artifact from any repositories" instead of the error of ResourceNotFoundException). I'd appreciate testing on the error reporting. I think what we have now is pretty good - can you find a specific example where it is not the case? - Brett John Casey wrote: > Why on earth would you remove the root causes from all of these > diagnosers?? Particularly the PuntDiagnoser? > > Often, the root cause is the only thing that makes any sense...the rest > is just heaps of string-literal shoulder-shrugs that are too digested to > be of any help. If we can't get at the root cause, especially when its > hiding behind something like MojoExecutionException, or some otherwise > undiagnosed exception (PuntDiagnoser), many problems will be a complete > mystery. Not to mention the MNG issues this will reopen... > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
