[
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348441#comment-348441
]
Herve Boutemy edited comment on MSITE-650 at 6/20/14 2:26 AM:
--------------------------------------------------------------
notice that all of this is caused by cobertura requiring a forked lifecycle,
re-running the tests in this forked context
if you disable cobertura for site reporting, you won't have any problem
or there should be a report mojo that doesn't fork lifecycle but only reports
on results taken from previous execution
was (Author: hboutemy):
notice that all of this is caused by cobertura requiring a forked lifecycle,
re-running the tests in this forked context
if you disable cobertura for site reporting, you won't have any problem
> Problem with multiple executions of surefire within site plugin 3.0
> -------------------------------------------------------------------
>
> Key: MSITE-650
> URL: https://jira.codehaus.org/browse/MSITE-650
> Project: Maven Site Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Kristian Rosenvold
> Fix For: backlog
>
> Attachments: fooproject.tar.gz, mvninstall_fooproject.txt,
> mvnsite_3.4-SNAPSHOT.txt, mvnsite_fooproject.txt,
> mvn_X_install_fooproject.txt, mvn_X_site_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
(v6.1.6#6162)
