Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

Make PMD cutoff levels configurable #5

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

hgschmie
Copy link

We are using jenkins as part of our internal build process and we recently decided to change the meanings of the PMD levels for our build. To make a long story short, we consider both 4 and 5 to be "low priority". However, it turns out that the Jenkins plugin for collecting PMD information has the mapping "1,2" -> HIGH, "3,4" -> NORMAL, "5" -> LOW hard coded.

This patch adds new configuration for both the PMD Reporter and the PMD Publisher to make the cutoffs for "HIGH" and "NORMAL" configurable. The defaults are the same as the hard coded values from the current plugin, so upgrading to this change should not change any behavior.

@hgschmie
Copy link
Author

@uhafner
Copy link
Member

uhafner commented Aug 5, 2018

Thanks for making the mapping configurable!

The PMD parser (and the associated plugin) has been integrated into the warnings plugin (see PMD tool descriptor). These changes are not yet released but I don't think that it makes sense to add any new functionality to the PMD plugin. It would make more sense to adapt your changes to the new API. What do you think? The FindBugs tool descriptor shows how to provide additional properties...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants