You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2007/03/29 22:41:40 UTC
[jira] Created: (MNG-2913) neither site lifecycle phase nor
site:run mojo triggers surefire tests to run when surefire-report is
configured
neither site lifecycle phase nor site:run mojo triggers surefire tests to run when surefire-report is configured
-----------------------------------------------------------------------------------------------------------------
Key: MNG-2913
URL: http://jira.codehaus.org/browse/MNG-2913
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.1-alpha-1
Reporter: John Casey
Priority: Blocker
it looks like the BuildPlanner is not taking into account forked lifecycles/executions when it injects report mojos into the mix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2913) neither site lifecycle phase nor
site:run mojo triggers surefire tests to run when surefire-report is
configured
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-2913:
----------------------------
Assignee: John Casey
Fix Version/s: 2.1-alpha-1
> neither site lifecycle phase nor site:run mojo triggers surefire tests to run when surefire-report is configured
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2913
> URL: http://jira.codehaus.org/browse/MNG-2913
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.1-alpha-1
> Reporter: John Casey
> Assigned To: John Casey
> Priority: Blocker
> Fix For: 2.1-alpha-1
>
>
> it looks like the BuildPlanner is not taking into account forked lifecycles/executions when it injects report mojos into the mix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2913) neither site lifecycle phase nor site:run
mojo triggers surefire tests to run when surefire-report is configured
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-2913.
---------------------------
Resolution: Fixed
reports now trigger forking properly.
> neither site lifecycle phase nor site:run mojo triggers surefire tests to run when surefire-report is configured
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2913
> URL: http://jira.codehaus.org/browse/MNG-2913
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.1-alpha-1
> Reporter: John Casey
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.1-alpha-1
>
>
> it looks like the BuildPlanner is not taking into account forked lifecycles/executions when it injects report mojos into the mix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira