You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:49:55 UTC
[jira] (MSITE-455) executedProject is not properly populated by
@execute in reporting
[ https://jira.codehaus.org/browse/MSITE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MSITE-455.
--------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> executedProject is not properly populated by @execute in reporting
> ------------------------------------------------------------------
>
> Key: MSITE-455
> URL: https://jira.codehaus.org/browse/MSITE-455
> Project: Maven Site Plugin
> Issue Type: Bug
> Reporter: Brett Porter
> Priority: Minor
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)