[
https://issues.apache.org/jira/browse/MNG-8196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8196:
---------------------------------
Description:
The boxing of `MojoException` into a `MojoExecutionException` brought two
issues:
1. It added another layer to the stacktrace, making it a bit less readable for
users and breaking test expectations for Maven extension authors (the latter
was my main motivation for this change)
2. It lost the `longMessage`, which meant that this message was no longer shown
at the end of the build.
This change fixes both problems by passing through the original `MojoException`
and treating this new exception type directly in `DefaultExceptionHandler` and
`MojoExecutor`
> Make exception messages match Maven 3 again
> -------------------------------------------
>
> Key: MNG-8196
> URL: https://issues.apache.org/jira/browse/MNG-8196
> Project: Maven
> Issue Type: Improvement
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-4
>
>
> The boxing of `MojoException` into a `MojoExecutionException` brought two
> issues:
> 1. It added another layer to the stacktrace, making it a bit less readable
> for users and breaking test expectations for Maven extension authors (the
> latter was my main motivation for this change)
> 2. It lost the `longMessage`, which meant that this message was no longer
> shown at the end of the build.
> This change fixes both problems by passing through the original
> `MojoException` and treating this new exception type directly in
> `DefaultExceptionHandler` and `MojoExecutor`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
