Howdy, AFAIR one of the reasons for these two exceptions were to distinguish cases like: * expected exception during execution of Mojo: most typical, uncompilable source, or bad config/param, or something alike, condition the user CAN (and should) fix, usually by editing sources, POM or settings. * unexpected exception during execution of Mojo: IO/permission, disk full, network, whatever -- this condition user MAY fix or may not be able to fix (ie. some remote resource is down)
Re Guillaume proposal: IMHO it lacks this distinction above.... T On Sat, Jul 9, 2022 at 9:56 PM Guillaume Nodet <gno...@apache.org> wrote: > I have the following proposal for the new API: > > > https://github.com/gnodet/maven/tree/m-api-immutable/api/maven-api-core/src/main/java/org/apache/maven/api/plugin > > Le sam. 9 juil. 2022 à 15:23, Slawomir Jaranowski <s.jaranow...@gmail.com> > a écrit : > > > Hi > > > > Today - Maven 3.8.6 both exception generate the same message: BUILD > FAILURE > > > > We have some inconsistencies in javadocs descriptions [1]. > > We also have the wrong description on guide page [2]. > > > > There was a discussion about it, some on slack, some on GitHub [3] and > > connected issue MNG-7351 [4] > > > > As I remember we want one exception for Mojo in Maven 4. > > > > So it will be good to make a decision about it and fix mentioned place to > > be consistent. > > > > > > [1] > > > > > https://maven.apache.org/ref/3.8.6/apidocs/org/apache/maven/plugin/Mojo.html#execute-- > > [2] > > > https://maven.apache.org/guides/plugin/guide-java-plugin-development.html > > [3] https://github.com/apache/maven/pull/632 > > [4] https://issues.apache.org/jira/browse/MNG-7351 > > > > -- > > Sławomir Jaranowski > > > > > -- > ------------------------ > Guillaume Nodet >
