PMD
kotlinx-kover | PMD | |
---|---|---|
4 | 22 | |
1,235 | 4,666 | |
3.6% | 0.9% | |
8.1 | 9.9 | |
6 days ago | 5 days ago | |
Kotlin | Java | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kotlinx-kover
-
Apache Maven JaCoCo Configuration
The tool to measure code coverage in Java is JaCoCo, but that is not the only one. There are existing things like OpenClover or in Kotlin things like Kover and so on (just to mention some).
-
Kover is a Gradle plugin for Kotlin code coverage tools (by Jetbrains IntelliJ). Does anyone try it? Is it ready for production in Android development?
Kover is still lacking basic Android support and in our Android projects we were not able to replace Jacoco yet (due to errors): https://github.com/Kotlin/kotlinx-kover/issues/18
-
Did anyone find a way to exclude compose previews from Jacoco code coverage?
Kover 0.6.1 now supports this: https://github.com/Kotlin/kotlinx-kover/issues/121
-
Ask HN: What is a modern Java environment?
- Language: Java 17 or Kotlin
- API Layer: For tiny projects, Vert.x API directly, for larger projects Quarkus
- DB: Postgres, in-memory H2 for simple stuff
- Testing: JUnit 5, Testcontainers to automatically start + stop DB Docker containers with tests, Mockito or Mockk (Kotlin) for mocks
- Dependency Injection: CDI (built into Quarkus, for Vert.x you can initalize Weld when the app starts)
- Build tool: Gradle with Kotlin DSL
- Other tools:
Kover: automatic code-coverage reports from JaCoCo/IntelliJ (https://github.com/Kotlin/kotlinx-kover)
PMD
-
We Have Code Quality At Home: Open Source Java Code Quality Tools
PMD is a source code static analysis tool. It inspects your Java files for any issues, and has a configurable set of rules to look at.
- PMD 7 Is Here
-
Amazon CodeGuru Reviewer: already time for retirement?
While the security findings can be pretty elaborate and helpful, the code quality and performance focused findings are not that impressive and can often be detected by more basic or powerful tools like SonarQube (paying) or PMD (free). To see what I mean you can have a look at the list of Java code quality detectors, which is pretty short and contains a lot of simple findings like:
-
Code Review for Flows
Also saw this convo has a couple years worth of ideas going on … https://github.com/pmd/pmd/issues/3413
-
Custom Gradle Plugin for Unified Static Code Analysis
PMD and Checkstyle are static analysis tools that check your code on each project build. Gradle allows to apply them easily.
-
Spring Boot – Black Box Testing
The generated classes should be put into .gitignore. Otherwise, if you have Checkstyle, PMD, or SonarQube in your project, then generated classes can violate some rules. Besides, if you don't put them into .gitignore, then each pull request might become huge due to the fact that even a slightest fix can lead to lots of changes in the generated classes.
-
After Java tutorials, now what???
- PMD Static Code Analysis tool: https://pmd.github.io/
-
Ask HN: What is a modern Java environment?
PMD, Spotbugs, Nullaway: Java linting/static analysis (https://pmd.github.io, https://spotbugs.github.io, https://github.com/uber/NullAway)
-
Code smell plugin
PMD, and checkstyle as well.
-
Writing Clean and Consistent Code with Static Analysis using PMD and Apex
Open up the config/ruleset.xml file, and you’ll find an XML document that lists several rules. These rules map to the issues which PMD will report on. Believe it or not, there are hundreds of Apex rules, and you can find the full set at the PMD repo. You have complete control over which rules to enable. Typically, you’d determine which ones are important by agreeing with your teammates on the ones that matter most. After all, their code will be statically analyzed, too!
What are some alternatives?
ktlint - An anti-bikeshedding Kotlin linter with built-in formatter
Spotbugs - SpotBugs is FindBugs' successor. A tool for static analysis to look for bugs in Java code.
kotlin - The Kotlin Programming Language.
SonarQube - Continuous Inspection
SDKMan - The SDKMAN! Command Line Interface
Error Prone - Catch common Java mistakes as compile-time errors
example-jacoco - Example Project to setup JaCoCo
Checkstyle - Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. By default it supports the Google Java Style Guide and Sun Code Conventions, but is highly configurable. It can be invoked with an ANT task and a command line program.
Quarkus - Quarkus: Supersonic Subatomic Java.
infer - A static analyzer for Java, C, C++, and Objective-C
Micronaut - Micronaut Application Framework
SonarJava - :coffee: SonarSource Static Analyzer for Java Code Quality and Security