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

Herve Boutemy commented on MSITE-650:
-------------------------------------

I think I found the cause:
http://maven.apache.org/ref/3.2.1/maven-core/xref/org/apache/maven/lifecycle/internal/DefaultLifecycleExecutionPlanCalculator.html#L461
{code:java}populateMojoExecutionConfiguration( project, forkedExecution, false 
);{code}
where
{code:java}private void populateMojoExecutionConfiguration( MavenProject 
project, MojoExecution mojoExecution, boolean allowPluginLevelConfig ){code}

so "false" should be "true"

now I need to write an IT for that, and that's the hard part...

I hope the fix will be in Maven 3.2.3 (or whatever the version will be)

And I'll need to create a MNG issue to track the issue in Maven core

> 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)

Reply via email to