[
https://issues.apache.org/jira/browse/MNG-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505906#comment-17505906
]
Herve Boutemy commented on MNG-7430:
------------------------------------
fixing the javadoc is necessary as a first step
we can also use the messages from Help to improve the description of the
semantics of each:
https://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException and
https://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
deprecating one or the other is an option: before deciding, I'd love to have
some facts about how much each of there exceptions are used in plugins
and "of course", we have an opportunity in Maven 4 to do some breaking change.
But let's start by Maven 3.9
> mark MojoExecutionException as deprecated
> -----------------------------------------
>
> Key: MNG-7430
> URL: https://issues.apache.org/jira/browse/MNG-7430
> Project: Maven
> Issue Type: Task
> Components: Core
> Reporter: Olivier Lamy
> Priority: Major
>
> since the start of Maven 3.x there is no more difference in the build
> result/output between MojoFailureException and MojoExecutionException.
> Even the javadoc is wrong as it says
> {quote}Throwing this exception causes a "BUILD ERROR" message to be
> displayed.{quote}
>
> https://github.com/apache/maven/blob/14ca7234380f81e54a5643082816048f3b6b67cf/maven-plugin-api/src/main/java/org/apache/maven/plugin/MojoExecutionException.java#L24
> which definitely never happen see sample here
> https://github.com/olamy/maven-exception-plugin
> we could mark it as deprecated for 3.9.x onward.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
