Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[MCHECKSTYLE-362] Add suppressionFileOptional configuration option to allow builds if file in suppressionsLocation is missing

Open
#274 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start by tracing the Maven Checkstyle Plugin configuration for suppressionsLocation and the handling of Checkstyle's SuppressionFilter optional flag. Verify how an unresolved suppression file is currently supplied to Checkstyle, then define done as accepting suppressionFileOptional and allowing the build to continue when the configured file is missing.

Written by the indexing model from the issue text.

Description

enhancement priority:minor

Marcus Watkins opened MCHECKSTYLE-362 and commented

We use a parent pom containing our checkstyle configuration but have a few projects with generated code that we'd like to exclude from checkstyle rules. This means we have to copy the whole checkstyle configuration into these projects' poms with a suppressionsLocation because adding it to the parent would fail the builds in projects where that file is missing.

Checkstyle itself has an optional flag on SuppressionFilter that allows it to continue if the supplied file is missing.

We'd like to extend the Maven Checkstyle Plugin to have similar functionality by way of a suppressionFileOptional configuration option that would simply skip supplying the file value to checkstyle if the file fails to resolve.

If this sounds like something you would accept let us know and we'll whip it up and submit a PR.


1 votes, 3 watchers

Dominant language
Java
Stars
98
Forks
69
Avg merge
2d 11h
Merged PRs (30d)
8

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-checkstyle-plugin

All issues in apache/maven-checkstyle-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.