Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
An “undefined configuration property” message does not have one standard meaning across code analysis scanners. The fastest way to diagnose it is to identify which component emitted the message, find which component owns the property, and check that component’s installed version and configuration scope. Then correct or remove the setting and verify that the intended analysis behavior actually changed.
Identify which component rejected the property
A scan can involve several configuration layers: the analyzer itself, a rule or checker, a build plugin, the build tool, an IDE integration, and a CI wrapper. A property name that looks plausible at one layer may be invalid at another. The error prefix, exception type, stack trace, task name, and build phase can help identify the component that parsed or rejected it.
Read the full diagnostic rather than relying on the phrase “undefined property.” It may mean the property does not exist, a required property has no value, its value has the wrong type, or it was placed in the wrong scope. Alternatively, the key may be accepted but not affect the scan because another setting overrides it. Depending on the tool, an unknown setting may cause a hard failure, a warning, or no visible error at all.
Recommended Free Tools
- A build-script exception points first to the build tool or plugin DSL; it does not by itself prove the analyzer rejected an option.
- A message naming a rule or checker suggests a rule-specific configuration issue.
- A wrapper or IDE may require its own option namespace or forwarding syntax before an analyzer receives the setting.
Check the property’s spelling, scope, and format
Look up the exact key in documentation or a schema for the component and version that are installed. Compare capitalization, punctuation, separators, prefixes, nesting, and expected value type. Do not assume similarly named properties at different layers are interchangeable.
Scanner options versus rule or checker options
Some properties configure the analyzer globally; others belong to one rule or checker and must be nested or prefixed accordingly. For example, Clang distinguishes analyzer configuration from checker-specific configuration and documents different option forms. When Clang is invoked through its driver, frontend arguments need the appropriate forwarding; CodeChecker also has its own analyzer- and checker-configuration options and prefixes. See the Clang analyzer options documentation for the syntax and its cautions: many non-default analyzer options are primarily for development and may not be supported as stable general-purpose settings.
PMD documents rule properties inside that rule’s <properties> element and says assigning a property that does not exist throws an error. Check the individual rule’s supported properties rather than treating them as global scanner options. In Checkstyle, properties belong to modules and can be inherited through the module hierarchy, so a property may be valid but ineffective—or invalid—if attached at the wrong point. The relevant references are PMD rule configuration and Checkstyle configuration.
Build-tool and wrapper settings
A plugin’s extension or task properties are a separate API from the analyzer’s own options unless the integration explicitly maps them. Gradle documents that undeclared properties can fail fast, while plugins expose configuration through their own extensions. Check the Gradle build-script documentation and the plugin’s extension documentation, such as Adding a plugin extension.
Also verify the syntax expected by the route you use to launch the analysis. A direct command-line flag may not pass through a build plugin, IDE, or CI wrapper unchanged. For command-line, XML, YAML, TOML, or EditorConfig settings, confirm that the key is written in the format and namespace the relevant component expects.
Check scanner, plugin, and wrapper versions separately
A property documented for a current analyzer may not exist in the version bundled with an older plugin or wrapper. Record the versions of the scanner, build plugin, and integration independently; then compare each with its own documentation, migration guide, and release notes. Look for properties that were added, renamed, removed, moved, or changed in type.
The SpotBugs Gradle plugin illustrates why this matters: its migration notes describe minimum Gradle versions for plugin releases and a v5-to-v6 change in which effort and reportLevel became enum values. Consult the plugin documentation and migration notes before changing a setting or upgrading. Avoid upgrading blindly if it could alter analysis behavior; align versions when the installed component lacks the documented option, and confirm compatibility constraints first.
Rank #4
Confirm the intended configuration file and precedence
A correctly named property will not help if the scanner loads a different file, if the setting is outside the selected project or module, or if a command-line, environment, parent-project, build, or CI value takes precedence. Check the working directory, explicit configuration-file argument, file path and format, and the exact arguments used by the build or CI job. Inspect quoting, escaping, wrapper prefixes, and argument boundaries too.
Free tools Windows power users keep installed
One-click scans. No signup required.
Maven is one example of why names can differ by layer: plugin configuration element names map to plugin goal parameter names, while command-line system-property names can differ. Many Maven plugins provide a help goal to show parameter names and types; the documented example is mvn javadoc:help -Ddetail -Dgoal=javadoc. Treat that as a Maven-specific diagnostic, not a universal scanner command. See Maven plugin configuration.
Best Value
.NET code analysis can likewise draw settings from analyzer configuration files and MSBuild properties, and third-party rules can define custom keys. Microsoft documents that setting AnalysisMode through MSBuild causes bulk configuration options in the analyzer config file to be ignored. In that situation, a key can be valid but not control the result you expect. Check the applicable configuration layer and precedence in Microsoft’s code analysis configuration options.
Apply the smallest correction and verify the result
- Capture the diagnostic and invocation. Record the exact message, file and line, command or CI step, configuration-file path, scanner version, and plugin or wrapper version. Redact secrets before sharing logs.
- Locate the emitting component. Use the diagnostic prefix, exception type, stack trace, task name, and build phase to identify which parser or configuration API raised the issue.
- Find the property’s owner. Check the installed-version documentation, schema, rule reference, plugin extension or task API, or build-tool help. Establish whether the key belongs to the scanner, rule, checker, plugin, build tool, or wrapper.
- Match the documented shape. Verify the exact spelling, case, prefix, nesting, value type, and file or command-line syntax. Confirm that the target rule or checker exists and is enabled if the setting is rule-specific.
- Check versions and precedence. Compare scanner, plugin, and wrapper versions with their migration notes. Confirm which configuration file is loaded and whether another source overrides the setting.
- Make one targeted change. Correct a verified typo, move the key to its documented scope, use the wrapper’s syntax, remove an unsupported setting, or select a documented equivalent. Do not substitute a similarly named property unless its meaning and version support are confirmed.
- Rerun the same workflow and check behavior. Confirm that the diagnostic is gone and, where possible, inspect the effective configuration or test for the expected analysis behavior. A successful exit code alone does not prove the option took effect.
Do not suppress the warning as a first fix. That can make a build look clean while leaving the intended setting unapplied. Suppression is appropriate only when the specific tool documents that behavior and you have established that ignoring the key is acceptable.
If the error persists
Reduce the configuration to the smallest example that still reproduces the problem. Include the exact diagnostic, sanitized invocation, relevant configuration fragment, and scanner, plugin, wrapper, and build-tool versions. Separate a parser rejection from a recognized setting that is misplaced, overridden, or ineffective; each points to a different correction. Use documentation for the exact installed versions, since live documentation may describe settings unavailable in an older release.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
