[
https://jira.codehaus.org/browse/MPMD-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356839#comment-356839
]
Michael Osipov edited comment on MPMD-193 at 11/24/14 2:54 PM:
---------------------------------------------------------------
Andreas, this is pretty nice. Does this properly guarantee that source files
will be read with that encoding, not just XML? Do you have already a timeframe
for 5.2.2? If that would happen anytime soon, I would file another issue to
uprade and roll a release by December.
was (Author: michael-o):
Andreas, this is pretty nice. This properly guarantees that source files will
be read with that encoding, not just XML? Do you have already a timeframe for
5.2.2? If that would happen anytime soon, I will file another issue to uprade
and roll a release by December.
> 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)
