You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Walco van Loon (JIRA)" <ji...@codehaus.org> on 2006/04/04 23:43:48 UTC

[jira] Updated: (MNG-2188) Report mojos should check canGenerateReport() when called directly

     [ http://jira.codehaus.org/browse/MNG-2188?page=all ]

Walco van Loon updated MNG-2188:
--------------------------------

    Attachment: AbstractMavenReport-canGenerateReport-check.patch

> Report mojos should check canGenerateReport() when called directly
> ------------------------------------------------------------------
>
>          Key: MNG-2188
>          URL: http://jira.codehaus.org/browse/MNG-2188
>      Project: Maven 2
>         Type: Improvement

>   Components: Sites & Reporting
>     Versions: 2.0.3
>     Reporter: Vincent Massol
>  Attachments: AbstractMavenReport-canGenerateReport-check.patch
>
>
> There's a canGenerateReport() method in a ReportMojo. This method is called by the site phase to decide if the mojo should be called or not. This is cool. However the user can call directly the report mojo and in that case the canGenerateReport() method is not called automatically. Thus the solution for a plugin developer is to write:
> {code}
> public void executeReport()
> {
>     if (canGenerateReport() )
>     { 
>         [...]
>     }
> }
> {code}
> Which means that the canGenerateReport method is going to be called twice when mvn site is executed.

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