[
https://issues.apache.org/jira/browse/MNG-8244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905172#comment-17905172
]
Guillaume Nodet commented on MNG-8244:
--------------------------------------
Those phases are currently only triggered when using the new concurrent builder
using {{mvn -b concurrent}}. I think that's because those phases are new and
don't map to the previous lifecycle.
> Using before:all / all / after:all is not triggered
> ---------------------------------------------------
>
> Key: MNG-8244
> URL: https://issues.apache.org/jira/browse/MNG-8244
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.0.0-beta-4
> Reporter: Karl Heinz Marbaise
> Priority: Major
> Fix For: 4.0.0-rc-2
>
>
> I just tried to use the phases: {{{}before:all{}}}, {{all}} and {{after:all}}
> simply to test at which exact point in time those phases are running.
> I've used things like {{{}before:integration-test{}}}, {{integration-test}}
> and {{after:integration-test}} which works fine also using
> {{{}before:build{}}}, {{build}} and {{after:build}} works so far fine.
>
> The only exeptions are the {{{}before:all{}}}, {{all}} and {{after:all}}
> which are not triggered.
>
> I have setup a full working example:
> [https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8244]
> During the execution with Maven 4.0.0-beta-4 I can see outputs which
> indicates that the phases are correctly triggered (except {{{}before:all{}}},
> {{all}} and {{{}after:all{}}}): The lines "--- echo:0.5.0:echo" are triggered
> by the appropriate life cycle phases...
> {code:java}
> ...
> [INFO]
> [INFO] --- jar:3.4.2:jar (default-jar) @ mng-8244 ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:
> /Users/khm/ws-git-soebes/maven-bugs/MNG-8244/target/mng-8244-2.0.0.jar
> [INFO]
> [INFO] --- site:3.12.1:attach-descriptor (attach-descriptor) @ mng-8244 ---
> [INFO] Skipping because packaging 'jar' is not pom.
> [INFO]
> [INFO] --- echo:0.5.0:echo (before-build) @ mng-8244 ---
> [INFO] Hallo 'before:build' phase.
> [INFO]
> [INFO] --- echo:0.5.0:echo (build) @ mng-8244 ---
> [INFO] Hallo 'build' phase.
> [INFO]
> [INFO] --- echo:0.5.0:echo (after-build) @ mng-8244 ---
> [INFO] Hallo 'after:build' phase.
> [INFO]
> [INFO] --- failsafe:3.3.1:integration-test (integration-test) @ mng-8244 ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- failsafe:3.3.1:verify (after:integration-test) @ mng-8244 ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- jacoco:0.8.12:report (default) @ mng-8244 ---
> [INFO] Skipping JaCoCo execution due to missing execution data file.
> [INFO] Copying com.soebes.maven.bugs:mng-8244:pom:2.0.0 to project local
> repository
> [INFO] Copying com.soebes.maven.bugs:mng-8244:jar:2.0.0 to project local
> repository
> [INFO] Copying com.soebes.maven.bugs:mng-8244:pom:consumer:2.0.0 to project
> local repository
> [INFO]
> --------------------------------------------------------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> --------------------------------------------------------------------------------------------------------------------------
> [INFO] Total time: 1.203 s
> [INFO] Finished at: 2024-09-07T12:16:36+02:00 {code}
>
> It could also be that the plugin I have written might not work on those
> particular phases... but my assumption is that this is not the issue here...
> (maybe I'm wrong)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
