[
https://issues.apache.org/jira/browse/MPLUGIN-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497678#comment-17497678
]
ASF GitHub Bot commented on MPLUGIN-394:
----------------------------------------
SebastianKuehn opened a new pull request #73:
URL: https://github.com/apache/maven-plugin-tools/pull/73
PluginReport didn't specify an encoding while reading the
Plugin-Descriptor. This causes the fallback to the plattform encoding
and ignores the (user specified) input encoding.
This commits adds an integration test to reproduce the error and fixes
it by using the input encoding for the creation of the used Reader.
The integration tests forces the plattform encoding to CP1252 (Western
European charset used in Windows) while the source (input) and output
encoding is UTF-8.
The source file contains non-ASCII characters which have a different
representation in both encodings.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Report-Mojo doesn't respect input encoding
> ------------------------------------------
>
> Key: MPLUGIN-394
> URL: https://issues.apache.org/jira/browse/MPLUGIN-394
> Project: Maven Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 3.6.4
> Reporter: Sebastian Kühn
> Priority: Major
>
> {{plugin:report}} reads the Plugin-XML-File with with the platform encoding
> instead of the specified input encoding. This results in an broken generated
> XDoc and finally Site.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
