maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Jira)" <>
Subject [jira] [Commented] (MNG-5668) post-<phase> should always be executed after <phase>
Date Sat, 23 Nov 2019 11:24:00 GMT


Hudson commented on MNG-5668:

Build unstable in Jenkins: Maven TLP » maven » mng-5668-poc #8


> post-<phase> should always be executed after <phase>
> ----------------------------------------------------
>                 Key: MNG-5668
>                 URL:
>             Project: Maven
>          Issue Type: Sub-task
>          Components: FDPFC, Plugins and Lifecycle
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Major
> Original proposal:
> {quote}
> There are right now 3 phases which also have a pre-<phase> and post-<phase>,
namely integration-test, clean and site. However, even if one has bound goals to the post-phases,
they're probably never called.
> When there's an integration-test starting up some server, you'd probably always want
to kill it no matter what happens during the IT (let say a NPE).
> The proposal is to execute the post-<phase> as the finally block in Java. If you
really want to execute only the integration-test without the post, the phase should be marked,
e.g. 'mvn [integration-test]', where the brackets lock the phase.
> {quote}

This message was sent by Atlassian Jira

View raw message