[
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348241#comment-348241
]
Pierre Cardoso commented on MSITE-650:
--------------------------------------
Hello, reporting again more than one year later. I upgraded my project to Maven
3.2.1, Site plugin 3.3, Surefire plugin 2.17, and Cobertura plugin 2.6. The
problem is still there.
Now, to sum it all up: it seems that, with "mvn install", the configurations
passed to each Surefire execution are the proper ones. But with "mvn site", the
configuration passed to each Surefire execution is the configuration of the
first Surefire execution, repeated for all. I am not able to say from where the
problem originates : Maven? The Surefire plugin? The site plugin? the Cobertura
plugin?
> 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
>
>
> 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)
