You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/04/25 06:43:00 UTC
[jira] [Closed] (MSITE-951) Don't abuse report's symbolic output name as filename
[ https://issues.apache.org/jira/browse/MSITE-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MSITE-951.
--------------------------------
Resolution: Fixed
Fixed with [fcb097d592d245701b9c1505c558844e14e44115|https://gitbox.apache.org/repos/asf?p=maven-site-plugin.git;a=commit;h=fcb097d592d245701b9c1505c558844e14e44115].
> Don't abuse report's symbolic output name as filename
> -----------------------------------------------------
>
> Key: MSITE-951
> URL: https://issues.apache.org/jira/browse/MSITE-951
> Project: Maven Site Plugin
> Issue Type: Bug
> Affects Versions: 4.0.0-M7
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 4.0.0-M8
>
>
> {{MavenReport#getOutputName()}} represents a symbolic name indepent of an output format. It is up to the current sink to create one. It must not be assumed that this value represents a file or an HTML file. This can only be done within the {{SiteRendererSink}} context. The other problem is that the symbolic name is used to key on pre-existing documents which are filenames thus it may happen that the report may overwrite a handwritten document.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)