Releases: stepstone-tech/sonar-coldfusion
2.2.0
2.1.1
2.1.0
2.0.0
1.7.1-SNAPSHOT
Sonarqube Coldfusion Plugin release
SonarQube ColdFusion Plugin 1.5.0
Includes CFLint 1.2.0 with a lot of fixes and updates.
Notably, the JAR is now smaller by over 2MB, because the CFLint package is smaller.
SonarQube ColdFusion Plugin 1.4.0
Includes CFLint 1.1.0 which comes primarily with fixes to handling semicolons.
SonarQube ColdFusion Plugin 1.3.0
Includes CFLint 1.0.1, which in turn comes with a number of bug fixes that were earlier breaking the content of cflint-result.xml
, causing issues with sonar-scanner analysis.
Technical Debt Estimations
Every issue now comes with a pre-set estimate of how much time it would take to resolve it -- including thinking about a resolution, implementing it and testing.
New Rules
CFLint 1.0.0 delivered a few new rules that are now available:
- Argument is missing a name -- when a function argument doesn't have a name.
- Star in SQL
SELECT
-- when an asterisk*
is used in aSELECT
query. - Never use
CFQUERY
in.cfm
files -- where a query is hard-coded into a.cfm
file, which should normally only be a view. - Use
displayName
instead ofname
-- where a component has aname
attribute, which is obsolete, as the name should originate from the file name. - Local literal value used too often -- when a locally scoped literal is used a number of times and should be replaced with a named variable.
- Global literal value used too often -- when a globally scoped literal is used a number of times and should be replaced with a named variable.
SonarQube ColdFusion Plugin 1.3.0-alpha-2
Comes with CFLint 1.0.1-SNAPSHOT built from cflint/CFLint@1c3c2d5. On top of the alpha-1 changes, this one contains fixes to previously reported Known Issues:
SonarQube ColdFusion Plugin 1.3.0-alpha-1
An alpha release including CFLint 1.0.0. See the "Known Issues" section.
New rules:
- Argument is missing a name
- Star in SQL
SELECT
- Never use
CFQUERY
in.cfm
files - Use
displayName
instead ofname
- Local literal value used too often
- Global literal value used too often
Known Issues
We found these to be blockers when using CFLint 1.0.0 with our code. They may not occur in your code.