You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/03/21 16:03:00 UTC
[jira] [Commented] (MNG-5668) post- should always be executed after
[ https://issues.apache.org/jira/browse/MNG-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829622#comment-17829622 ]
ASF GitHub Bot commented on MNG-5668:
-------------------------------------
gnodet opened a new pull request, #1448:
URL: https://github.com/apache/maven/pull/1448
- **Lifecycle API**
- **[MNG-5668] Proof of concept implementation of dynamic phases (wip)**
> post-<phase> should always be executed after <phase>
> ----------------------------------------------------
>
> 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
> 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
(v8.20.10#820010)