You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/10/18 18:12:00 UTC

[jira] [Commented] (MNG-5693) Change logging of MojoExceptions to console

    [ https://issues.apache.org/jira/browse/MNG-5693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216332#comment-17216332 ] 

Michael Osipov commented on MNG-5693:
-------------------------------------

Classes to be touched:

* org.apache.maven.exception.DefaultExceptionHandler
* org.apache.maven.exception.ExceptionSummary
* org.apache.maven.exception.DefaultExceptionHandlerTest

> Change logging of MojoExceptions to console
> -------------------------------------------
>
>                 Key: MNG-5693
>                 URL: https://issues.apache.org/jira/browse/MNG-5693
>             Project: Maven
>          Issue Type: Improvement
>          Components: FDPFC, Plugin API
>            Reporter: Robert Scholte
>            Assignee: Sylwester Lachiewicz
>            Priority: Major
>             Fix For: 3.7.0-candidate
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> If a plugin fails for any reason, a general message is logged with a reference to a wiki page, which never contains the real reason why the plugin failed.
> For new users this is very confusing. Even when we teach them to read, and they finally see a link, it's quite frustrating for them that they still don't know what happened.
> {{MojoExecutionException}} and {{MojoFailureException}} should never refer to a wikipage anymore.
> Plugin writers should get more control over the message written to the console.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)