gwizard
kotlinx-kover | gwizard | |
---|---|---|
4 | 2 | |
1,235 | 109 | |
3.6% | -0.9% | |
8.1 | 0.0 | |
6 days ago | 11 months ago | |
Kotlin | Java | |
Apache License 2.0 | - |
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)
gwizard
-
The Reason Java Is Still Popular
Here's what I generally use when doing greenfield development in Java:
https://github.com/gwizard/gwizard
I wrote it, so feel free to consider me biased. That said, "wrote" is a strong word, it just glues some other projects together with Guice. Not much actual code there. Which may be the answer to your question - if you asked me what's wrong with other frameworks, "too much code" is a decent answer.
-
Ask HN: What is a modern Java environment?
I have been thinking of writing up a series of articles on this. Without going into too much detail:
* IDEA
* Deploy on Google App Engine, Digital Ocean App Platform, Heroku, Elastic Beanstalk, etc - get out of the ops business entirely.
* Guice as the backbone, no Spring/Boot. I wrote a tiny dropwiard-like "framework" to make this easier: https://github.com/gwizard/gwizard but there's a laughable amount of code here, you could build it all from scratch with minimal effort. This is about as lightweight as "frameworks" get because Guice does the heavy lifting.
* JAX-RS (Resteasy) for the web API. IMO this is the best part of Java web development. HTTP endpoints are simple synchronous Java methods (with a few annotations) and you can test them like simple Java methods.
* Lombok. Use @Value heavily. Cuts most of the boilerplate out of Java.
* Junit5 + AssertJ. (Or Google Truth, which is almost identical to AssertJ).
* Use functional patterns. Try to make all variables and fields final. Use collections streams heavily. Consider vavr.io (I'll admit I haven't it in anger yet, but I would in a new codebase).
* StreamEx. Adds a ton of useful stream behavior; I don't even use basic streams anymore.
* Guava. There's just a lot of useful stuff here.
* For the database, it really depends on what you're building. Most generic business apps, postgres/hibernate/guice-persist/flyway. Yeah, folks complain about hibernate a lot but it's a decent way to map to objects. Use SQL/native queries, don't bother with JPQL, criteria queries, etc.
* Hattery for making http requests (https://github.com/stickfigure/hattery). This is another one of mine. I make zillions of http requests, functional/immutable ergonomics really matter to me.
* Github actions for CI.
* Maven for the build. Yes, it's terrible, except for every other build system is worse. Gradle seems like it should be better but isn't. I'd really love some innovation here. Sigh.
What are some alternatives?
ktlint - An anti-bikeshedding Kotlin linter with built-in formatter
prime-mvc - Prime MVC is a high performance Model View Controller framework built in Java.
kotlin - The Kotlin Programming Language.
NullAway - A tool to help eliminate NullPointerExceptions (NPEs) in your Java code with low build-time overhead
SDKMan - The SDKMAN! Command Line Interface
orm16 - Code generation-based approach to ORM for Java 17, focusing on records as persistent data model
example-jacoco - Example Project to setup JaCoCo
JHipster - JHipster, much like Spring initializr, is a generator to create a boilerplate backend application, but also with an integrated front end implementation in React, Vue or Angular. In their own words, it "Is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures."
Quarkus - Quarkus: Supersonic Subatomic Java.
Micronaut - Micronaut Application Framework
reactor-core - Non-Blocking Reactive Foundation for the JVM