[ 
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320570#comment-320570
 ] 

Pierre Cardoso commented on MSITE-650:
--------------------------------------

I have the same sort of problem in a project of mine (surefire with several 
executions, all fine with install, all wrong with site); I'm not sure it's 
really the same, so, without going into details now, I'll just add some 
comments :
- For my project, the problem only happens with Maven 3 (it runs fine with 
Maven 2.2.1).
- For my project, running "mvn -X" shows that something is wrong with the 
properties : properties of execution X override the defaults in execution Y 
(unless they are already explicitly declared in Y).

Sorry if this is not very clear, I'm a bit short on time now.
I'll try to have a look at the [#SUREFIRE-905] project to see if it's indeed 
the same problem as mine.
Thanks.
                
> Problem with multiple executions of surefire within site plugin 3.0
> -------------------------------------------------------------------
>
>                 Key: MSITE-650
>                 URL: https://jira.codehaus.org/browse/MSITE-650
>             Project: Maven 2.x and 3.x 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

Reply via email to