[
http://jira.codehaus.org/browse/MTAGLIST-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MTAGLIST-29.
-------------------------------------
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.2
Fixed in r6348.
> Fix handling of output directory
> --------------------------------
>
> Key: MTAGLIST-29
> URL: http://jira.codehaus.org/browse/MTAGLIST-29
> Project: Maven 2.x Taglist Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 2.2
>
> Attachments: directory-handling.patch
>
>
> As for the outpuDirectory parameter:
> - its type should be File instead of String (see also [Common
> Bugs|http://www.nabble.com/Common-Bugs-to14783703s177.html])
> - it should NEVER be queried by the mojo. It may be used by the user to
> specify the output path if the mojo is run standalone but during a site
> build, the site plugin sets the output directory via
> MavenReport.setReportOutputDirectory(). For this reason,
> MavenReport.getReportOutputDirectory() should be called to access the
> EFFECTIVE output directory. AbstractMavenReport will return the original
> outputDirectory parameter value (by calling getOutputDirectory()) if the mojo
> is called standalone.
> - the expression "${project.reporting.outputDirectory}" should be used
> instead of the hard-coded "${project.build.directory}/site"
> - there is no need to create the output directory in the mojo, it's done when
> setting up the Sink for the report
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
