[
https://issues.apache.org/jira/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17284974#comment-17284974
]
Herve Boutemy edited comment on MSITE-650 at 2/15/21, 11:07 PM:
----------------------------------------------------------------
as seen before, it's related to forked lifecycle
we need a MNG issue to track update in Maven core
and I fear that current behaviour of forked lifecycle:
1. is a feature in the case of Cobertura for example, where we want multiple
executions of forked lifecycle because it creates different output results
2. is a problem in the case of Maven Site Plugin, where we want only 1
execution because every execution is expected to git the same output
then this issue is tricky to have a magic "fix"
what you can do is avoid forked lifecycles
was (Author: hboutemy):
as seen before, it's related to forked lifecycle
we need a MNG issue to track update in Maven core
and I fear that current behaviour of forked lifecycle:
1. is a feature in the case of Cobertura for example, where we want multiple
executions of forked lifecycle because it creates different output results
2. is an issue in the case of Maven Site Plugin, where we want only 1 execution
because every execution is expected to git the same output
then this issue is tricky to have a magic "fix"
what you can do is avoid forked lifecycles
> Problem with multiple executions of surefire within site plugin 3.0
> -------------------------------------------------------------------
>
> Key: MSITE-650
> URL: https://issues.apache.org/jira/browse/MSITE-650
> Project: Maven Site Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Kristian Rosenvold
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: backlog
>
> Attachments: fooproject.tar.gz, mvn_X_install_fooproject.txt,
> mvn_X_site_fooproject.txt, mvninstall_fooproject.txt,
> mvnsite_3.4-SNAPSHOT.txt, mvnsite_fooproject.txt
>
>
> There is a test project attached to SUREFIRE-905 that has a total of 4
> executions of surefire, with different configuration for each.
> When running "mvn clean install" inside this project, surefire gets executed
> 4 times as expected. When running "mvn site" only the first execution gets
> run, the last three get stopped by the configuration-checksum in surefire,
> indicating they get executed with the *same* configuration as the default
> execution. (Surefire creates a SHA1 hash of all the mojo parameters to avoid
> re-running the same configuration, which is why I conclude the three
> executions get the same configuration as the default config)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
