You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2014/03/26 21:26:59 UTC

[jira] (MNG-5593) Plugin Errors are not handled

    [ https://jira.codehaus.org/browse/MNG-5593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343699#comment-343699 ] 

Robert Scholte commented on MNG-5593:
-------------------------------------

I've just had a false positive (exit code 0 which should have been 1) when testing the integration-tests of the enforcer project. However, a second run completed as expected. So I don't have a valid reproducible test yet.

> Plugin Errors are not handled
> -----------------------------
>
>                 Key: MNG-5593
>                 URL: https://jira.codehaus.org/browse/MNG-5593
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.2.1
>            Reporter: Michael Schnupp
>            Priority: Critical
>
> The [DefaultBuildPluginManager|https://maven.apache.org/ref/3.2.1/maven-core/xref/org/apache/maven/plugin/DefaultBuildPluginManager.html#L133] executes the plugin mojo and catches all kind of exceptions.
> However if the plugin throws some Error, it is not catched and maven continues like everything went fine.
> Shouldn't maven handle Errors and stop the build in that case?
> (see also IZPACK-1050)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)