You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2025/03/27 13:37:00 UTC

[jira] [Updated] (MNG-5668) Always run `after:xxx` phase if `before:xxx` phase has been started

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

Guillaume Nodet updated MNG-5668:
---------------------------------
    Summary: Always run `after:xxx` phase if `before:xxx` phase has been started  (was: post-<phase> should always be executed after <phase>)

> Always run `after:xxx` phase if `before:xxx` phase has been started
> -------------------------------------------------------------------
>
>                 Key: MNG-5668
>                 URL: https://issues.apache.org/jira/browse/MNG-5668
>             Project: Maven
>          Issue Type: Sub-task
>          Components: FDPFC, Plugins and Lifecycle
>            Reporter: Robert Scholte
>            Priority: Major
>             Fix For: 4.0.0-rc-4
>
>
> 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
(v8.20.10#820010)