[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356806#comment-356806 ]
Michael Osipov commented on MPMD-193: ------------------------------------- Does this solve the problem? Is the encoding parameter used through out PMD/CPD? If so, I would merge this one. Can you kindly file a ticket with PMD requesting not to modify the System environment. This may cause unpleasant behavior. > 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 added in PMD 5.1.1. > 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)