Hi @jma ,
I think I’m able to replicate what you are doing now. It seems that when the severity is changed to “INFO” instead of the default “MAJOR”, then the issue will persist and ignore the custom
maximumLineLength value. That is a minor bug that we can handle. I’ll report this to the devs.
EDIT: Actually, INFO level makes sense. From Issues:
Neither a bug nor a quality flaw, just a finding.
That means it’s a finding and not a true “issue” issue. Can you try adjusting the severity to not be INFO and see if the issue disappears (modify the quality profile, make sure the project uses that quality profile, rescan)?
EDIT: Oops, I reviewed your last screenshot that shows the issue with CRITICAL severity. I’ll add this to the notes when I mention it to the devs:
- If the severity is left as the default MAJOR, then the adjusted maximumLineLength value is respected.
- If any other severity is chosen (BLOCKER, CRITICAL, MINOR, INFO), then the adjusted maximumLineLength value is ignored and the issue is shown.