Filter problems in mimaFindBinaryIssues #793
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
mimaFindBinaryIssues
does not apply the problem filters. This means that the output ofmimaFindBinaryIssues
may be inconsistent with what is reported bymimaReportBinaryIssues
(ie, the former may be non-empty although the latter would not report any issue). Is that intentional?In
sbt-version-policy
we have to re-implement the problem filtering because of that behavior.Note that applying the filters in
mimaFindBinaryIssues
would require more changes than this commit: the code that implements the reporting part would have to be updated accordingly (currently, it takes the filters as parameters, and it prints the number of problems that have been filters out).Another way to reduce the code duplication between
sbt-version-policy
andmima
would be to make the methodProblemReporting.isReported
public.How would you like to proceed? Apply the filtering in
mimaFindBinaryIssues
, makeProblemReporting.isReported
public, or do nothing?