java.lang.IllegalStateException: The field 'format' does not exist or is not annotated with @RuleProperty in the class org.sonar.plugin.typescript.rules.ClassName

After a recent upgrade we are seeing the following error during scans for a Maven project.

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
 **SonarQube version: 9.0.1**
 **sonar-maven-plugin:3.9.0.2155:sonar**
  • error observed (wrap logs/code around triple quote ``` for proper formatting)
Caused by: java.lang.IllegalStateException: The field 'format' does not exist or is not annotated with @RuleProperty in the class org.sonar.plugin.typescript.rules.ClassName
    at org.sonar.api.batch.rule.Checks.configureFields (Checks.java:170)
    at org.sonar.api.batch.rule.Checks.instantiate (Checks.java:154)
    at org.sonar.api.batch.rule.Checks.addAnnotatedChecks (Checks.java:128)
    at org.sonar.plugin.typescript.TypeScriptRules.<init> (TypeScriptRules.java:251)
    at org.sonar.plugin.typescript.ExternalTypescriptSensor.execute (ExternalTypescriptSensor.java:80)
    at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse (AbstractSensorWrapper.java:48)
    at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute (ModuleSensorsExecutor.java:85)
    at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1 (ModuleSensorsExecutor.java:59)
    at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy (ModuleSensorsExecutor.java:77)
    at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute (ModuleSensorsExecutor.java:59)
    at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart (ModuleScanContainer.java:79)
    at org.sonar.core.platform.ComponentContainer.startComponents (ComponentContainer.java:137)
    at org.sonar.core.platform.ComponentContainer.execute (ComponentContainer.java:123)
    at org.sonar.scanner.scan.ProjectScanContainer.scan (ProjectScanContainer.java:382)
  • steps to reproduce
 mvn -X sonar:sonar -Dsonar.host.url=http://x.x.x.x:9000/ -Dsonar.verbose=true -Dsonar.log.level=DEBUG
  • potential workaround

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour