New / Changed

• Based on db* CODECOP v5.0.1
  • see Release Notes
  • see Trivadis PL/SQL & SQL Coding Guidelines Version 4.4.

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 10.4.1

Client Plugin

• Minimum db* CODECOP Validators version: 5.0.1
• Latest db* CODECOP Validators version tested: 5.0.1

New / Changed

• Based on db* CODECOP v5.0.0
  • see Release Notes
  • see Trivadis PL/SQL & SQL Coding Guidelines Version 4.4.

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 10.4.1

Client Plugin

• Minimum db* CODECOP Validators version: 5.0.0
• Latest db* CODECOP Validators version tested: 5.0.0

New / Changed

• Based on db* CODECOP v4.5.0
  • see Release Notes

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 10.3.0

Client Plugin

• Minimum db* CODECOP Validators version: 4.5.0
• Latest db* CODECOP Validators version tested: 4.5.0

New / Changed

• Based on db* CODECOP v4.4.2
  • see Release Notes

Fixed

• #11 StringIndexOutOfBoundsException when analyzing an empty file with sonar-scanner

New / Changed

• Based on db* CODECOP v4.4.0
  • see Release Notes

Fixed

• Crashes during analysis with sonar-scanner
  • IllegalArgumentException: 0 is not a valid line for a file during processing. (#8)
  • StringIndexOutOfBoundsException while processing .md files. (#9)
• License expiration not reported (validity time and supported version).

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 10.2.1

Client Plugin

• Minimum db* CODECOP Validators version: 4.4.0 (older versions will not work when no checks are overridden)
• Latest db* CODECOP Validators version tested: 4.4.0

Fixed

#7 Not a valid line for pointer

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 9.8.0

Client Plugin

• Minimum db* CODECOP Validators version: 4.3.0 (older versions will not work)
• Latest db* CODECOP Validators version tested: 4.3.1

New

• Based on db* CODECOP v4.3.0

  • see Release Notes

• PLSQLCOP-294: Support code duplication metrics and syntax highlighting in the standalone plugin

  • Registering syntax highlighting tokens
  • Register CPD (copy & paste duplication) tokens for
    • Create Function
    • Create Package Body
    • Create Procedure
    • Create Trigger
    • Create Type Body
    • Create View
  • Code duplication is detected and recorded by SonarQube

• PLSQLCOP-295: Support code coverage in the standalone plugin

  • Use core metrics to save number of statements
  • Process also test files (sonar.tests), see analysis parameters
  • Register executable lines (lines to be covered) for the following object types supported by utPLSQL:
    • Create Function
    • Create Package Body
    • Create Procedure
    • Create Trigger
    • Create Type Body
  • Process the code coverage report produced by utPLSQL-cli by setting the property sonar.coverageReportPaths when running sonar-scanner

Fixed

• PLSQLCOP-432: Missing log entries in debug mode

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 9.6.1

Client Plugin

• Minimum db* CODECOP Validators version: 4.3.0 (older versions will not work)
• Latest db* CODECOP Validators version tested: 4.3.0

New

• Based on db* CODECOP v4.2.4
  • see Release Notes

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 9.2.1

Client Plugin

• Minimum db* CODECOP Validators version: 4.0.0
• Latest db* CODECOP Validators version tested: 4.2.1

New

• Based on db* CODECOP v4.2.3
  • see Release Notes

Fixed

• PLSQLCOP-401: NPE when using NOSONAR marker to suppress G-9501 on execute immediate

• PLSQLCOP-402: Possible NPE while loading SQALE XML file (CWE 476)

  • There are no known problems, but it is theoretically possible when information where missing in XML file (e.g. for custom validators)

• PLSQLCOP-409: Validator in SonarQube uses wrong character set

  • The system property sonar.sourceEncoding was not considered when parsing SQL & PL/SQL files, this could cause parse errors, e.g. for string literals using quote delimiter characters such as q'£ .... £'.
  • The character set detected by SonarQube is now propagated to the SQL & PL/SQL parser

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 9.2.1

Client Plugin

• Minimum db* CODECOP Validators version: 4.0.0
• Latest db* CODECOP Validators version tested: 4.2.1

New

• Based on db* CODECOP v4.2.2
  • see Release Notes

Compatibility

SonarQube

• Minumum SonarQube version: 7.9
• Latest SonarQube version tested: 9.0.1

Client Plugin

• Minimum db* CODECOP Validators version: 4.0.0
• Latest db* CODECOP Validators version tested: 4.2.1