Releases: Ericsson/CodeCheckerEclipsePlugin
Stability improvements
- SWT GUI Testing suite was added
- Checker configuration was replaced by CodeChecker analyzer parameter passthrough
- CodeChekcer 6.10 support
- Refactorings
- Bug Fixes
v0.0.6
Major architectural changes!
Lot of architecture changes were made to simplify the way how the plugin runs the analyzers through CodeChecker and parses the results. This should increase the plugin performance and stability.
Changes
- Support CodeChecker v6.8 and v6.8.1 to run the analysis.
- Remove of the CodeChecker backend server #115 #116
CodeChecker server instances were required to run in the background for each project, this added a lot of extra complexity to the plugin. With the new architecture CodeChecker is only used to run the analysis and the plugin parses the generated plist reports. - CodeChecker service api layer was removed
The CodeChecker server api layer is not needed in the new plist parsing architecture - Easier version increment
No manual xml modification is required to increment the plugin version. - General documentation and source code comment improvements
Bug fix release
Copy the jar file into the dropin folder of eclipse.
Start like this: ./eclipse -clean (to reread the updated plugin file)
This release contains a single bug fix
-analysis was not always running correctly due to this bug:
#106
Enhanced alpha release
Copy the jar file into the dropin folder of eclipse.
Start like this: ./eclipse -clean (to reread the updated plugin file)
Various enhancements
-On eclipse "project clean", the CodeChecker DB is removed. This allows cleaning up the results in case the results suck in (CodeChecker version change)
-log4j logging was removed and now Eclipse PDE log is used (logs are available from eclipse "error" window)
-fixed various bugs related to refreshing the check results.
Logging rewritten to PDE
-Logging rewritten from log4j to the standard Plugin Development Environment logging
-Null pointer exception related to configuration fixed.
Configuration fixes
-CodeChecker configuraiton is refactored
-some exceptions are fixed
Installation
Place the jar file into the dropins folder of eclipse. Restart eclipse using the "-clean" switch.
Note:
this is a testing release only, not for production use.
This is the first testing release
This first beta release is for testing purposes only.
The following can be configured in the plugin
-Clang SA/Clang Tidy allowed Checkers
-CodeChecker path
-Python environment path