[Closed] (MINVOKER-225) strange message ordering in case of post-build script failure

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Closed] (MINVOKER-225) strange message ordering in case of post-build script failure

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/MINVOKER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MINVOKER-225.
-----------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s: 3.1.1

Fixed in [7ac7c580bc666873d029989e64b2a5e75ae31b04|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commit;h=7ac7c580bc666873d029989e64b2a5e75ae31b04]

> strange message ordering in case of post-build script failure
> -------------------------------------------------------------
>
>                 Key: MINVOKER-225
>                 URL: https://issues.apache.org/jira/browse/MINVOKER-225
>             Project: Maven Invoker Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.0.1
>            Reporter: HervĂ© Boutemy
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 3.1.1
>
>
> example:
> {noformat}[INFO] Building: non-default-config/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO]           non-default-config/pom.xml ....................... FAILED (1.8 s)
> [INFO]   The post-build script returned false.{noformat}
> I would have expected
> {noformat}[INFO] Building: non-default-config/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] the post-build script returned false.
> [INFO]           non-default-config/pom.xml ....................... FAILED (1.8 s){noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)