You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/02/02 21:21:57 UTC
[jira] Updated: (MCHECKSTYLE-82) Clarify usage of outputDirectory
parameter
[ http://jira.codehaus.org/browse/MCHECKSTYLE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MCHECKSTYLE-82:
-----------------------------------------
Attachment: MCHECKSTYLE-82.zip
I tried to reproduce the bug you described with the attached project, but failed. The {{CheckstyleReport}} overwrites {{setReportOutputDirectory()}} to sync its instance field {{outputDirectory}} with the directory for the site, so I wonder how it should deviate.
> Clarify usage of outputDirectory parameter
> ------------------------------------------
>
> Key: MCHECKSTYLE-82
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-82
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Improvement
> Affects Versions: 2.1
> Reporter: Benjamin Bentmann
> Priority: Trivial
> Attachments: MCHECKSTYLE-82.zip, output-directory.patch
>
>
> The plugin's documentation should state that the parameter "outputDirectory" is ONLY evaluated for standalone runs of a mojo and is ignored when run during a site generation. Otherwise, confusion is likely.
--
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