[
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330947#comment-330947
]
Petr Bodnar commented on MSITE-650:
-----------------------------------
I wonder if there is any progress after one year...?
I have probably exactly the same problem with Maven 3.0.5,
cobertura-maven-plugin 2.5.1 and surefire 2.11. All (e. g. "mvn
cobertura:cobertura", additional test executions defined via a maven profile)
worked well when using Maven 2.2.1...
Can somebody tell whether Cobertura somehow internally uses the Site plugin
(tested with 3.3)? If not, then this would lead us to a problem in the Maven
core itself? Provided that the surefire plugin checks its executions for
duplicates well...
And the final question: can the following commit be somehow related to the bug?
http://mail-archives.apache.org/mod_mbox/maven-surefire-commits/201103.mbox/%[email protected]%3E
(author = bug reporter, to my surprise :)).
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
