[MSITE-998] MavenReport#setReportOutputDirectory(File) is called too late

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0-M12
• Fix Version/s: 3.20.0, 4.0.0-M13, 4.0.0-beta-1
• Component/s: localization, property interpolation
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 14/Dec/23 11:17
• Updated: 20/Jul/24 18:20
• Resolved: 14/Dec/23 12:05

Description

Consider you report performs some actions based on the updated value of the report output directory in #canGenereateReport(). E.g., Maven PMD Plugin does first write status files to that directory and to determine the location of XRef files. Since #canGenereateReport() happens before ##setReportOutputDirectory(File) is invoked the calculation is partially wrong. This can happen when the site is rendered for a non-default locale or after MSHARED-1327 where there is now a clean distinction between standalone execution and site execution, especially for external reports which properly needs the report output directory set. Reports which use a preconfigured sink aren't affected.

All setters on the MavenReport need to be invoked first before any (internal) execution can happen. Prior to that all reports need to be evaluated on a per-locale basis.

Issue Links

• is caused by: MSHARED-1327 Change default value of output directory in AbstractMavenReport