Re: [pmd-devel] Custom rule set issue in my Azure DevOps pipeline

[Juan M. S. D. <jua...@gm...>]

Yes, simply remove them

On Sun, Nov 10, 2024, 1:19 AM Abhinav kumar <abh...@gm...>
wrote:

> Hello Juan,
>
> Thank you so much for the response, so what should be the next step?
> In Place of these properties  " cc_categories,
> cc_remediation_points_multiplier, cc_block_highlighting  "  what should
> be used because these are all custom defined rule sets we are using in our
> project.
>
> Should we remove these properties from our file, will that work?
>
> Awaiting your response.
>
> Regards,
> Abhinav
>
> On Thu, Nov 7, 2024 at 6:59 PM Juan Martín Sotuyo Dodero <
> jua...@gm...> wrote:
>
>> Abhinav,
>>
>> PMD 7 is a major release, and as such, introduces breaking changes.
>> As per our own policy, we never introduce a breaking change unless the
>> relevant feature has already been deprecated in the previous release, and
>> ensuring appropriate warnings are emitted with it’s usage, even if still
>> supported, with the intention of giving people time to accommodate and
>> prepare. Aditionally, with any release, the release notes
>> <https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html>
>> comprehensively cover these changes.
>>
>> As per the error’s self description
>>
>> 2024-11-04T07:40:49.3666791Z  11|          <property name="cc_categories" value="Complexity" />
>> 2024-11-04T07:40:49.3667364Z               ^^^^^^^^^ Cannot set non-existent property 'cc_categories' on rule ExcessiveClassLength
>>
>> In this particular case, this is the relevant piece
>> <https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html#changed-rules:~:text=Apex%20General%20changes>
>> :
>>
>> *Apex General changes*
>>
>>    - The properties cc_categories, cc_remediation_points_multiplier,
>>    cc_block_highlighting have been removed from all rules. These
>>    properties have been deprecated since PMD 6.13.0. See issue #1648
>>    <https://github.com/pmd/pmd/issues/1648> for more details.
>>
>> Hope that helps. Checking the logs for deprecation warnings can hopefully
>> help you stay prepared for major changes without affecting your workflows.
>>
>> Regards
>>
>> On Thu, Nov 7, 2024 at 6:24 AM Abhinav kumar <abh...@gm...>
>> wrote:
>>
>>> Hello Team,
>>>
>>> I am using sfdx-scanner for my project and custom PMD rule set for the
>>> static code analysis.
>>> When I upgraded the scanner to 4.0.0, PMD was upgraded to 7.0.0 but then
>>> I started getting errors in my pipeline. The same rule set is working fine
>>> with the sfdx-scanner 3.25 version. I have attached the error log file.
>>>
>>> Also, I am attaching the custom ruleset file for your reference.
>>>
>>>
>>> _______________________________________________
>>> Pmd-devel mailing list
>>> Pmd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pmd-devel
>>>
>>