[MPMD-349] Upgrade Maven Reporting API to 3.1.1/Maven Reporting Impl to 3.2.0 by michael-o · Pull Request #84 · apache/maven-pmd-plugin (original) (raw)

added a commit that referenced this pull request

Aug 12, 2022

@michael-o

…to 3.2.0

This closes #84

@michael-o michael-o changed the titleMpmd 349 [MPMD-349] Upgrade Maven Reporting API to 3.1.1/Maven Reporting Impl to 3.2.0

Aug 12, 2022

michael-o added a commit that referenced this pull request

Aug 13, 2022

@michael-o

…to 3.2.0

This closes #84

michael-o added a commit that referenced this pull request

Aug 13, 2022

@michael-o

…to 3.2.0

This closes #84

michael-o added a commit that referenced this pull request

Aug 14, 2022

@michael-o

…to 3.2.0

This plugin hasn't been touched testwise for a very long time. The testing approach from MPIR has been applied to accommodate M-R-Impl 3.2.0 and future versions of it. The negative effect is that the parameter 'sourceEncoding' has duplicated 'inputEncoding' from AbstractMavenReport for a long time. For the sake of consistency it has been replaced with 'inputEncoding' which breaks backward compatibility. User where advised to use ${project.build.sourceEncoding} anyway.

This also upgrades for ITs:

This closes #84

michael-o added a commit that referenced this pull request

Aug 14, 2022

@michael-o

…to 3.2.0

This plugin hasn't been touched testwise for a very long time. The testing approach from MPIR has been applied to accommodate M-R-Impl 3.2.0 and future versions of it. The negative effect is that the parameter 'sourceEncoding' has duplicated 'inputEncoding' from AbstractMavenReport for a long time. For the sake of consistency it has been replaced with 'inputEncoding' which breaks backward compatibility. Users are advised to use ${project.build.sourceEncoding} anyway.

This also upgrades for ITs:

This closes #84

@michael-o

…to 3.2.0

This plugin hasn't been touched testwise for a very long time. The testing approach from MPIR has been applied to accommodate M-R-Impl 3.2.0 and future versions of it. The negative effect is that the parameter 'sourceEncoding' has duplicated 'inputEncoding' from AbstractMavenReport for a long time. For the sake of consistency it has been replaced with 'inputEncoding' which breaks backward compatibility. Users are advised to use ${project.build.sourceEncoding} anyway.

This also upgrades for ITs:

This closes #84

slawekjaranowski

slawekjaranowski

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})