[
https://jira.codehaus.org/browse/MNG-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347312#comment-347312
]
Tamás Cservenák commented on MNG-5640:
--------------------------------------
Am more concerned by Jason's comment on MNG-5389: "Just for clarification the
participant is meant to mutate the session, or projects within the session so
there's no reason at that point to alter the session.".
Basically am in same situation as Olivier (mutation happens based on some
external resource, and cleanup is needed too), so am unsure do I misuse
participant here and should go with EventSpy, or this is a bug?
> AbstractMavenLifecycleParticipant#afterSessionEnd is not invoked in some cases
> ------------------------------------------------------------------------------
>
> Key: MNG-5640
> URL: https://jira.codehaus.org/browse/MNG-5640
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 3.2, 3.2.1
> Reporter: Tamás Cservenák
> Attachments: aftersessionend.zip
>
>
> It seems that {{AbstractMavenLifecycleParticipant#afterSessionEnd}} is not
> invoked in some cases, at least one case for sure: when the build fails.
> Reproduce case:
> 1. unzip the attached project
> 2. build it but skip tests {{mvn clean install -Dtest=void
> -DfailIfNoTests=false}}
> 3. install the resulting jar in /lib/ext of your Maven 3.2.1
> 4. with JAR installed in Maven, build it again with skipped tests
> 5. verify console output (both {{afterProjectsRead OK}} and {{afterSessionEnd
> OK}} are printed on console)
> 6. with JAR installed in Maven, build it again with tests (there is one UT
> that always fails).
> 6. console output contains only {{afterProjectsRead OK}}, but afterSessionEnd
> method is NOT invoked.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
