Re: MojoExecutionException and MojoFailureException

Here you go. https://issues.apache.org/jira/browse/MSHARED-1032 On Mon, 11 Jul 2022, 20:21 Benjamin Marwell, wrote: > > Please note there are more exceptions, e.g. in reporting. That's always > been a problem. Not sure, but I must have opened an issue for this > somewhere. > > Just for the s

Re: MojoExecutionException and MojoFailureException

Please note there are more exceptions, e.g. in reporting. That's always been a problem. Not sure, but I must have opened an issue for this somewhere. Just for the sake of completeness. On Mon, 11 Jul 2022, 14:12 Guillaume Nodet, wrote: > Yes, that's why I only kept a single exception in the ne

Re: MojoExecutionException and MojoFailureException

Yes, that's why I only kept a single exception in the new API. Le lun. 11 juil. 2022 à 13:59, Romain Manni-Bucau a écrit : > It got aligned AFAIK -> > > https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/MojoExecutor.java#L382 > > Romain Mann

Re: MojoExecutionException and MojoFailureException

It got aligned AFAIK -> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/lifecycle/internal/MojoExecutor.java#L382 Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: MojoExecutionException and MojoFailureException

I might be wrong, but in case of "build FAILURE" only a short error is printed saying user should enable -X while with "BUILD ERROR" the exception is printed, maybe with a hint not to blame maven :-) Am 11.07.22 um 13:43 schrieb Romain Manni-Bucau: Hi, In all discussions about this topic it s

Re: MojoExecutionException and MojoFailureException

Hi, In all discussions about this topic it seems that this distinctions never had been useful so there seems to be an agreement to get a single exception "something went wrong in the mojo". Guess at the end being finer grain is not that useful for end user and makes writing mojo harder but I agree

Re: MojoExecutionException and MojoFailureException

Howdy, and along this line... BUILD FAILURE - uncompilable source, test failed, badly configured plugin, missing something from build, etc. all the issues that user CAN (and should) fix to have build pass, usually by editing sources, POM or settings. BUILD ERROR - disk full, no perm to write to d

Re: MojoExecutionException and MojoFailureException

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.

Re: MojoExecutionException and MojoFailureException

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 a écrit : > Hi > > Today - Maven 3.8.6 both exception generate the same message: BUI

MojoExecutionException and MojoFailureException

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

[m2] difference between MojoExecutionException and MojoFailureException?

MojoFailureException Javadoc = An exception occuring during the execution of a plugin. MojoExecutionException Javadoc = An exception occuring during the execution of a plugin. It apepars that a Failure can not have an Exception cause. But otherwise the two are identical. When would I use a Mo