Parser and static source code analyzer for PL/SQL and Oracle SQL.
This version is compatible with SonarQube 9.9 LTS and SonarQube 10.5 Community Edition.
It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.5.0-SNAPSHOT.jar (requires Java 11+) to test the parser and view the AST.
This version is compatible with SonarQube 9.9 LTS and SonarQube 10.5 Community Edition.
It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.4.0.jar (requires Java 11+) to test the parser and view the AST.
This version is compatible with SonarQube 9.9 LTS and SonarQube 10.4 Community Edition.
It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.3.1.jar (requires Java 11+) to test the parser and view the AST.
This version is compatible with SonarQube 9.9 LTS and SonarQube 10.4 Community Edition.
It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
sonar.zpa.file.suffixes
was renamed to sonar.plsqlopen.file.suffixes
due to changes in SonarQube 10.4.Plugin-RequiredForLanguages
to plsqlopen
. See the Gradle example here and the Maven example here.Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.3.0.jar (requires Java 11+) to test the parser and view the AST.
This version supports SonarQube 8.9 LTS and newer.
Please be aware that ZPA is only tested with SonarQube Community Edition. It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.2.1.jar (requires Java 11+) to test the parser and view the AST.
This version supports SonarQube 8.9 LTS and newer.
Please be aware that ZPA is only tested with SonarQube Community Edition. It may work with the commercial editions of SonarQube, but you won't be able to use ZPA and the embedded PL/SQL plugin from SonarSource to analyze the code simultaneously. If you need this scenario, please use zpa-cli instead.
Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin
.
Download the zpa-toolkit-3.2.0.jar (requires Java 11+) to test the parser and view the AST.
Fixes:
Install/update instructions:
sonar-zpa-plugin-3.1.1.jar
file to SONARQUBE_HOME/extensions/plugins.For custom plugin developers:
This version Improves performance on multi-core processors (#153). This option can be disabled through the SonarQube UI on "General Settings" > "Z PL/SQL Analyzer" > "Enable concurrent execution" or setting the property sonar.zpa.concurrentExecution=false
.
This version supports SonarQube 7.6 and newer and it's the last release supporting SonarQube 7.6. Please be aware that ZPA is only tested with SonarQube Community Edition. It may work with the commercial editions of SonarQube, but you'll have to choose if you want to use ZPA or SonarPLSQL (from SonarSource). You can't use both plugins to analyze the code simultaneously.
The next release will require SonarQube 8.9 LTS as minimum version.
Install/update instructions:
sonar-zpa-plugin-3.1.0.jar
file to the SONARQUBE_HOME/extensions/plugins.sonar-plsql-open-plugin*.jar
or sonar-zpa*.jar
) from that directory.For custom plugin developers:
New rules:
Other highlights:
This version supports SonarQube 7.6 and newer. Please be aware that ZPA is only tested with SonarQube Community Edition. It may work with the commercial editions of SonarQube, but you'll have to choose if you want to use ZPA or SonarPLSQL (from SonarSource). You can't use both plugins to analyze the code simultaneously.
Install/update instructions:
sonar-zpa-plugin-3.0.0.jar
file to the SONARQUBE_HOME/extensions/plugins.sonar-plsql-open-plugin*.jar
) from that directory.For custom plugin developers:
This version supports SonarQube 6.7 and newer and it's the last release supporting SonarQube 6.7. Also note that ZPA is only tested with SonarQube Community Edition. It may work with SonarQube Developer/Enterprise/Data Center Editions, but you'll have to choose between ZPA and SonarPLSQL. If you want a better support for commercial editions of SonarQube please see the issue #133 and contact me.
Some rule improvements, like:
Other highlights:
sonar.plsql.*
properties are not recognized anymore. Please use sonar.zpa.*
in the SonarQube Scanner.For custom plugin developers:
org.sonar.plugins.plsqlopen.api.annnotations.
-> org.sonar.plugins.plsqlopen.api.annotations.