Skip to content

Fix sbt load warnings by excluding unused lint keys#3029

Merged
He-Pin merged 1 commit into
mainfrom
fix/sbt-load-warnings-clean
May 31, 2026
Merged

Fix sbt load warnings by excluding unused lint keys#3029
He-Pin merged 1 commit into
mainfrom
fix/sbt-load-warnings-clean

Conversation

@He-Pin
Copy link
Copy Markdown
Member

@He-Pin He-Pin commented May 31, 2026

Motivation

sbt load was showing 165 warnings about unused keys, which cluttered the output and made it harder to identify real issues.

Modification

Added to to exclude the following keys from checks:

  • (used for linking to API docs)
  • (used to add timestamps to log output)
  • (used to filter projects for unidoc generation)
  • (used for PR validation)
  • (used to disable doclint for tests)

Result

sbt load now completes without any warnings about unused keys.

Tests

  • Verified sbt load completes without warnings

References

None - housekeeping

Motivation:
sbt load was showing 165 warnings about unused keys, which cluttered the output and made it harder to identify real issues.

Modification:
Added Global / excludeLintKeys to build.sbt to exclude the following keys from lintUnused checks:
- projectInfoVersion (used for linking to API docs)
- logManager (used to add timestamps to log output)
- unidocProjectFilter (used to filter projects for unidoc generation)
- fork (used for PR validation)
- javacOptions (used to disable doclint for tests)

Result:
sbt load now completes without any warnings about unused keys.

Tests:
- Verified sbt load completes without warnings

Refs: None - housekeeping
Copy link
Copy Markdown
Member

@pjfanning pjfanning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@He-Pin He-Pin merged commit 7c1d0a6 into main May 31, 2026
9 checks passed
@He-Pin He-Pin deleted the fix/sbt-load-warnings-clean branch May 31, 2026 20:00
@He-Pin
Copy link
Copy Markdown
Member Author

He-Pin commented Jun 6, 2026

@pjfanning I will backport this to 1.7.x

@pjfanning
Copy link
Copy Markdown
Member

@He-Pin why do we need this in 1.x? It is useful in main branch but 1.x branches are not very active and used for occasional patches.
I backported the test fix because the CI tests were failing too often on 1.7 branch.

@He-Pin
Copy link
Copy Markdown
Member Author

He-Pin commented Jun 6, 2026

Because I don't want to see the warning @pjfanning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants