[
https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=357487#comment-357487
]
Andreas Dangel commented on MPMD-193:
-------------------------------------
Yes, this internally sets `setSourceEncoding` - and this is used to read the
files. There is a bit confusion going on in the CPD Configuration, as the same
encoding property is used for the output (e.g. for the XML Renderer) - which
probably should be separated at some point. But the maven-pmd-plugin anyway
doesn't use the renderer, so it is not affected by this.
I plan to release PMD 5.2.2 in about 2 weeks.
> CPD's sourceEncoding not set since PMD 5.1.1 is used
> ----------------------------------------------------
>
> Key: MPMD-193
> URL: https://jira.codehaus.org/browse/MPMD-193
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: CPD
> Affects Versions: 3.2, 3.3, 3.4
> Reporter: Tweea Tang
> Attachments: CpdReport.java.patch,
> CpdReport.java(setSourceEncoding).patch
>
>
> Since PMD 5.1.1, CPDConfiguration adds a method postContruct().
> This method is used to set the sourceEncoding property used to read source
> files in PMD.
> If the sourceEncoding not set, CPD will use the platform default encoding to
> read the source files and maven-pmd-plugin's encoding has no effects.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
