[ https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356835#comment-356835 ]
Andreas Dangel commented on MPMD-193: ------------------------------------- The issue in PMD will be fixed with 5.2.2 (commit https://github.com/pmd/pmd/commit/afc13b29a20036ffbdabc13753e952807be7e91e) Either `setEncoding` or `setSourceEncoding` needs to be called. If you change the plugin to call `setSourceEncoding`, it should already work with the current PMD version (5.2.1). > 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)