[ http://jira.codehaus.org/browse/MSITE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl moved MNG-3016 to MSITE-446: ------------------------------------------ Complexity: (was: Intermediate) Component/s: (was: Sites & Reporting) Fix Version/s: (was: 2.2.x) Affects Version/s: (was: 2.0.6) (was: 2.0.4) (was: 2.0.5) Key: MSITE-446 (was: MNG-3016) Project: Maven 2.x Site Plugin (was: Maven 2 & 3) > Even external reports using AbstractMavenReport / MavenReport html with > isExternalReport() returning true create an empty html file target link > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: MSITE-446 > URL: http://jira.codehaus.org/browse/MSITE-446 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Reporter: iosif > Priority: Minor > Attachments: junit_temp.zip > > > To create an "external" report for maven, we have the method public boolean > isExternalReport() return true in an AbstractMavenReport subclass or > MavenReport implementation. The name of this html file is given by the > method getOutputName(). > I don't think an external report should need to generate this empty html file > just so the Maven site sidebar for reports has a target to link to. In more > than once instance, the generation of this empty html file has disrupted the > creation of the external report's html intro page of the same name. > Check out and install the attached project to your local repository, then add > it as a reporting plugin to some other project and run the site phase. Note > that target/site/empty_report.html has been created for this external 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