You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/12/31 07:39:55 UTC

[jira] Moved: (MSITE-455) executedProject is not properly populated by @execute in reporting

     [ http://jira.codehaus.org/browse/MSITE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-3032 to MSITE-455:
-----------------------------------------

          Component/s:     (was: Sites & Reporting)
        Fix Version/s:     (was: 2.x)
                       3.0-alpha-1
    Affects Version/s:     (was: 2.0.6)
                  Key: MSITE-455  (was: MNG-3032)
              Project: Maven 2.x Site Plugin  (was: Maven 2 & 3)

> executedProject is not properly populated by @execute in reporting
> ------------------------------------------------------------------
>
>                 Key: MSITE-455
>                 URL: http://jira.codehaus.org/browse/MSITE-455
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>            Reporter: Brett Porter
>            Priority: Minor
>             Fix For: 3.0-alpha-1
>
>
> saw this in the clirr plugin before adjusting.
> Had:
> @execute phase="compile"
> And a parameter:
> @parameter expression="${executedProject}"
> When running mvn site this was populated, and the forked lifecycle occurs, but the compile source roots do not contain values that should have been added on a project like maven-model, nor does it include the original source roots. However, when run as clirr:clirr (a normal mojo), it is populated correctly.

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