[
https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-650:
--------------------------------
Attachment: mvnsite_3.4-SNAPSHOT.txt
thank you Pierre for these tests: now I can see what you are talking about
I updated the test to use maven-site-plugin 3.4-SNAPSHOT and Maven 3.2.2
(currently being voted on), which have better output of the execution, then I
attach the output
here is a summary (I skipped less useful output lines):
{noformat}[INFO] --- maven-site-plugin:3.4-SNAPSHOT:site (default-site) @
fooproject ---
[INFO] configuring report plugin org.codehaus.mojo:cobertura-maven-plugin:2.5.2
[INFO] preparing 'cobertura' report requires '[cobertura]test' forked phase
execution
[INFO]
[INFO] >>> cobertura-maven-plugin:2.5.2:cobertura > [cobertura]test @
fooproject >>>
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
fooproject ---
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ fooproject
---
[INFO] --- cobertura-maven-plugin:2.5.2:instrument @ fooproject ---
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
fooproject ---
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ fooproject ---
[INFO] Surefire report directory:
/home/herve/Téléchargements/fooproject/target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running com.mycompany.fooproject.UnitTest
UnitTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec - in
com.mycompany.fooproject.UnitTest
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (comp-tests) @ fooproject ---
[INFO] Skipping execution of surefire because it has already been run for this
configuration
[INFO]
[INFO] --- maven-surefire-plugin:2.17:test (sys-tests) @ fooproject ---
[INFO] Skipping execution of surefire because it has already been run for this
configuration
[INFO]
[INFO] <<< cobertura-maven-plugin:2.5.2:cobertura < [cobertura]test @
fooproject <<<
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.7
[INFO] Rendering site with org.apache.maven.skins:maven-default-skin:jar:1.0
skin.
[INFO] Generating "Cobertura Test Coverage" report ---
cobertura-maven-plugin:2.5.2:cobertura
[INFO] Cobertura Report generation was successful.
[INFO] Generating "About" report ---
maven-project-info-reports-plugin:2.7:index{noformat}
it show that the problem happens during test lifecycle fork for cobertura
report preparation, ie ">>> cobertura-maven-plugin:2.5.2:cobertura >
[cobertura]test": yes, during this forked lifecycle, injection of configuration
for different executions of surefire:test mojo is not consistent
so it seems like a bug inside Maven core, for forked lifecycles
I need to investigate further on that, but wanted to share this first step
> 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)
