You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2012/08/18 14:02:21 UTC
[jira] (MSITE-650) Problem with multiple executions of surefire
within site plugin 3.0
Kristian Rosenvold created MSITE-650:
----------------------------------------
Summary: 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-650) Problem with multiple executions of surefire
within site plugin 3.0
Posted by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306590#comment-306590 ]
Kristian Rosenvold commented on MSITE-650:
------------------------------------------
I'm not sure I understand how that can lead to 4 identical executions of the surefire plugin. The checksum is designed to prevent identical re-executions, so it's doing what it was designed for. And the 4 executions are *supposed* to be different. Is there something I totally miss about how the site plugin works ??
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-650) Problem with multiple executions of surefire
within site plugin 3.0
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306600#comment-306600 ]
Dennis Lundberg commented on MSITE-650:
---------------------------------------
I'm not sure myself what triggers the execution of maven-surefire-plugin during the site phase. But I guess it must somehow be triggered by maven-site-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 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-650) Problem with multiple executions of surefire
within site plugin 3.0
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306498#comment-306498 ]
Dennis Lundberg commented on MSITE-650:
---------------------------------------
I've had a look at the Surefire mojos. AbstractSurefireMojo has the checksum calculator in it, but AbstractSurefireReportMojo does not and it does not inherit from AbstractSurefireMojo either. Judging by that the behavior is correct, because the configuration is the same when you do not include the configuration of maven-surefire-report-plugin in the calculation.
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-650) Problem with multiple executions of surefire
within site plugin 3.0
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSITE-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308641#comment-308641 ]
Herve Boutemy commented on MSITE-650:
-------------------------------------
this one seems to be related to MJAVADOC-171
> 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: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira