# Gradle

Gradle is an open-source build system and build tool used by developers to build software, including Java, Android, and Kotlin projects.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Gradle Build Cache Guide: Zero-Config CI Caching | Harness

DevFeed: [Gradle Build Cache Guide: Zero-Config CI Caching | Harness](<https://devfeed.tech/articles/gradle-build-cache-guide-zero-config-ci-caching-harness-146730.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/fast-ci-master-gradle-build-caching>)

Author: Hemanth Mantri

Published: 2026-11-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [build times](<https://devfeed.tech/topics/build-times.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [buildcache](<https://devfeed.tech/tags/buildcache.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [can](<https://devfeed.tech/tags/can.md>), [ci](<https://devfeed.tech/tags/ci.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [guide](<https://devfeed.tech/tags/guide.md>), [harness](<https://devfeed.tech/tags/harness.md>), [intelligence](<https://devfeed.tech/tags/intelligence.md>), [leveraging](<https://devfeed.tech/tags/leveraging.md>), [management](<https://devfeed.tech/tags/management.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [remote](<https://devfeed.tech/tags/remote.md>), [simplify](<https://devfeed.tech/tags/simplify.md>), [speed](<https://devfeed.tech/tags/speed.md>), [zero](<https://devfeed.tech/tags/zero.md>)

### AI overview

Gradle's build cache can reuse task outputs across workspaces when the task's declared inputs and outputs produce a matching cache key; custom Java tasks can opt in with `@CacheableTask`. Reliable hits depend on declaring all files and properties read or written, keeping inputs deterministic, and using relative path sensitivity to avoid checkout-path differences. Sharing a local cache across teammates or CI requires remote-cache setup. The excerpt says Harness CI Build Intelligence offers a managed remote cache enabled at the pipeline stage, with the Harness agent detecting tools and managing configuration and secure storage. It supports Gradle, Maven 3.9+, Bazel, and Go. Adding `--profile` makes cache savings visible in Harness dashboards; caching works without it, but savings are not displayed. These product capabilities are presented in the supplied excerpt.

### Source excerpt

Speed up Gradle builds with Harness CI's Build Intelligence, leveraging zero-config remote caching to reduce build times and simplify cache management. | Blog

## Migrating a Real Android App to Kotlin Multiplatform 4/4 -- Shipping WebAssembly to Productio

DevFeed: [Migrating a Real Android App to Kotlin Multiplatform 4/4 -- Shipping WebAssembly to Productio](<https://devfeed.tech/articles/migrating-a-real-android-app-to-kotlin-multiplatform-4-4-shipping-webassembly-to-productio-140455.md>)

Original publisher: [Read original article](<https://proandroiddev.com/migrating-a-real-android-app-to-kotlin-multiplatform-4-4-shipping-webassembly-to-productio-e863738a8151?source=rss----c72404660798---4>)

Author: Daniel Voko

Published: 2026-11-17T19:49:30Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [compose-for-web](<https://devfeed.tech/topics/compose-for-web.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [sqldelight](<https://devfeed.tech/topics/sqldelight.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [production](<https://devfeed.tech/tags/production.md>), [splash-screen](<https://devfeed.tech/tags/splash-screen.md>), [the-web](<https://devfeed.tech/tags/the-web.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

A Kotlin Multiplatform app that builds for WebAssembly still needs browser-specific production work. The excerpt describes an inline HTML splash screen for a roughly 19 MB bundle, a spinner with visible timeout and error states instead of a misleading byte-based progress bar, and browser-history navigation whose fragment routes must stay synchronized with backend redirects. It also covers a server-side image proxy needed because Strava's CDN lacks CORS headers, with requests tagged by client so native apps keep using original URLs. In the browser, SQLDelight uses sql.js with a hand-maintained schema mirror, creating a risk that schema changes break web only. A deployed-origin `blob:` media issue required a custom Coil mapper and fetcher. These examples show how browser loading, routing, security, storage and media behavior can affect architecture and maintenance.

### Source excerpt

The wasm build runs locally in minutes. ./gradlew wasmJsBrowserDevelopmentRun, a browser tab opens, the app is there. It feels finished. It isn't, and the reason is the subject of this article. The browser isn't a fourth target that happens to render the same Compose code. It's a host with its own rules about what paints when, who owns navigation, what a page is allowed to fetch, and what a database even is. Compose Multiplatform hides none of that -- it just gets your UI onto the canvas, and then you're in someone else's house. Getting a multiplatform app to build is different from making it production-ready. Everything below is a thing that worked locally and didn't work for users. Nothing paints until the bundle arrives On Android, the launcher draws your icon the instant the user taps it. The OS owns that moment, and you get it for free. On the web you get nothing. A blank page, for as long as it takes to fetch a wasm bundle -- around 19MB -- uncompressed, and around 6.5MB Brotli transfer size -- and compile it. Users don't read that as "loading", they read it as broken, and they leave before the first frame. So the first thing I had to write for the web was something Android had given me for a decade: a splash screen. It lives inline in index.html, CSS and all, specifically so it costs no request of its own -- a splash that waits on a stylesheet defeats the purpose. The color values are a hand-copied duplicate of the theme tokens in core:designsystem, so the canvas takes over without a colour change. It's duplication I'd normally reject, and here there's no alternative: the theme lives in Kotlin inside the bundle that hasn't downloaded yet. It also has a known flaw I decided to keep. The splash follows the OS colour scheme, while the app also honours a theme the user picked by hand in settings. Someone who forced the theme against their OS gets one flash at the handover. Reading their choice would mean parsing the stored settings JSON from plain JavaScript, and coup

## Debug Your Dart in a Java Debugger, and JFX Central on a Phone

DevFeed: [Debug Your Dart in a Java Debugger, and JFX Central on a Phone](<https://devfeed.tech/articles/debug-your-dart-in-a-java-debugger-and-jfx-central-on-a-phone-130301.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/debug-dart-in-a-java-debugger/>)

Author: Shai Almog

Published: 2026-11-12T00:00:00Z

Content type: news

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Dart](<https://devfeed.tech/topics/dart.md>), [Java](<https://devfeed.tech/topics/java.md>), [JavaFX](<https://devfeed.tech/topics/javafx.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [iphone](<https://devfeed.tech/topics/iphone.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [acceptance-tests](<https://devfeed.tech/tags/acceptance-tests.md>), [api](<https://devfeed.tech/tags/api.md>), [apps](<https://devfeed.tech/tags/apps.md>), [array](<https://devfeed.tech/tags/array.md>), [async](<https://devfeed.tech/tags/async.md>), [background](<https://devfeed.tech/tags/background.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [browser](<https://devfeed.tech/tags/browser.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [dart](<https://devfeed.tech/tags/dart.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debugger](<https://devfeed.tech/tags/debugger.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [java](<https://devfeed.tech/tags/java.md>), [phone](<https://devfeed.tech/tags/phone.md>), [port](<https://devfeed.tech/tags/port.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Codename One's Dart-to-Java builds now map Java class debug information back to Dart source, so standard Java debuggers show Dart files and line numbers and can resolve breakpoints without a Dart debugger or IDE plugin. The post also reports fixes from importing real Flutter apps, including Dart language and runtime gaps, and Gradle import support. Its JavaScript port improves selected compute benchmarks while matching JVM checksums; several attempted optimizations were dropped after tests showed no benefit or slower results, and integer division by zero now throws Java's ArithmeticException. Finally, porting JFX Central to iPhone surfaced JavaFX compatibility-layer fixes for property listeners, remote images, text wrapping, CSS sizing, and bound visibility. The author notes the phone port is less polished than an app built for Codename One from the start.

### Source excerpt

Flutter apps built by Codename One now debug in Dart, in the standard Java debugger. Plus Flutter fixes from a real port, a faster web port and JFX Central on an iPhone.

## Clean Up Your Conditional Logic: Exploring Kotlin 2.5.0-Beta2's New Boolean & Nullable Utilities

DevFeed: [Clean Up Your Conditional Logic: Exploring Kotlin 2.5.0-Beta2's New Boolean & Nullable Utilities](<https://devfeed.tech/articles/clean-up-your-conditional-logic-exploring-kotlin-2-5-0-beta2-s-new-boolean-nullable-utilities-122284.md>)

Original publisher: [Read original article](<https://proandroiddev.com/clean-up-your-conditional-logic-exploring-kotlin-2-5-0-beta2s-new-boolean-nullable-utilities-7854207156ea?source=rss----c72404660798---4>)

Author: Nav Singh

Published: 2026-11-07T16:39:54Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [conditionals](<https://devfeed.tech/topics/conditionals.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [if statement](<https://devfeed.tech/topics/if-statement.md>), [Null-Safety](<https://devfeed.tech/topics/null-safety.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [scope function](<https://devfeed.tech/topics/scope-function.md>)

Tags: [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apply](<https://devfeed.tech/tags/apply.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [boolean](<https://devfeed.tech/tags/boolean.md>), [chaining](<https://devfeed.tech/tags/chaining.md>), [clean-code](<https://devfeed.tech/tags/clean-code.md>), [condition](<https://devfeed.tech/tags/condition.md>), [data-class](<https://devfeed.tech/tags/data-class.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [functions](<https://devfeed.tech/tags/functions.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-2](<https://devfeed.tech/tags/kotlin-2.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [let](<https://devfeed.tech/tags/let.md>), [receiver](<https://devfeed.tech/tags/receiver.md>), [scope-functions](<https://devfeed.tech/tags/scope-functions.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>)

### AI overview

Kotlin 2.5.0-Beta2 introduces experimental standard-library helpers for conditional work: `onTrue` and `onFalse` run a supplied block when a Boolean matches, then return that Boolean unchanged; `ifOrNull` lazily computes and returns a value when its condition is true, or returns null when false. The excerpt shows using the Boolean helpers for authentication side effects and `ifOrNull` to produce a phone number only when contact information is available. Use requires opting in to `ExperimentalStdlibApi`, either at the function or file level or through Gradle language settings. The excerpt does not establish broader API availability or stability.

### Source excerpt

AI generated image Ditch redundant if-else boilerplate and awkward scope chaining with the newly introduced onTrue(), onFalse(), and ifOrNull() functions. Kotlin has always excelled at eliminating boilerplate. From concise data classes and standard scope functions (apply, also, let, takeIf) to smart casting, the language consistently seeks ways to make everyday idioms more expressive. Kotlin 2.5.0-Beta2 adds standard library functions that let us inspect a value before returning it, or return a nullable result based on that value. https://kotlinlang.org/docs/whatsnew-eap.html?utm_campaign=kotlin-releases&utm_content=2-5-0-beta2 Boolean.onTrue(action: () -> Unit): Boolean Boolean.onFalse(action: () -> Unit): Boolean ifOrNull(condition: Boolean, action: () -> T): T? Implementation Because these functions are introduced as experimental APIs in the standard library, we need to opt in to use them. File/Function Annotation OptIn(ExperimentalStdlibApi::class) Module-wide via Gradle config kotlin { sourceSets.all { languageSettings.optIn("kotlin.ExperimentalStdlibApi") } }onTrue() & onFalse() Both functions invoke a supplied block when the receiver matches the condition and return the original boolean unmodified. Example data class User(val id: String, val email: String) class AuthService() { // Before: fun authenticateLegacy(user: User, token: String): Boolean { val isValid = verifyToken(user.email, token) if (isValid) { "Auth.success" } else { "Auth.failure" } return isValid } // Now: @OptIn(ExperimentalStdlibApi::class) fun authenticate(user: User, token: String): Boolean = verifyToken(user.email, token) .onTrue { "Auth.success" } .onFalse { "Auth.failure" } }ifOrNull() When shaping API responses or DTOs, we may return one computed value if a flag is true and another if false. Traditionally, this looks like 👇 val phoneNumber = if (user.hasContactInfo) user.phoneNumber else nullThe New Way: ifOrNull() ifOrNull(condition) { //.. } lazily evaluates the lambda block only if

## Clean Up Your Conditional Logic: Exploring Kotlin 2.5.0-Beta2's New Boolean & Nullable Utilities

DevFeed: [Clean Up Your Conditional Logic: Exploring Kotlin 2.5.0-Beta2's New Boolean & Nullable Utilities](<https://devfeed.tech/articles/clean-up-your-conditional-logic-exploring-kotlin-2-5-0-beta2-s-new-boolean-nullable-utilities-122052.md>)

Original publisher: [Read original article](<https://proandroiddev.com/clean-up-your-conditional-logic-exploring-kotlin-2-5-0-beta2s-new-boolean-nullable-utilities-7854207156ea?source=rss-711ab22c5c77------2>)

Author: Nav Singh

Published: 2026-11-07T02:22:10Z

Content type: tutorial

Language: en

Sources: [Nav Singh](<https://devfeed.tech/sources/stories-by-nav-singh-on-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [conditionals](<https://devfeed.tech/topics/conditionals.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [if statement](<https://devfeed.tech/topics/if-statement.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [scope function](<https://devfeed.tech/topics/scope-function.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [boolean](<https://devfeed.tech/tags/boolean.md>), [clean-code](<https://devfeed.tech/tags/clean-code.md>), [conditional](<https://devfeed.tech/tags/conditional.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-2](<https://devfeed.tech/tags/kotlin-2.md>), [standard-library](<https://devfeed.tech/tags/standard-library.md>)

### AI overview

Kotlin 2.5.0-Beta2 introduces three experimental standard-library utilities for conditional logic. `Boolean.onTrue` and `onFalse` run a supplied block when the Boolean matches, then return the original Boolean unchanged; the excerpt shows them used to trigger authentication messages while preserving the verification result. `ifOrNull(condition) { ... }` evaluates its block only when the condition is true, returning its value or `null`, as in the phone-number example. Use requires opting in with `ExperimentalStdlibApi`, either at a file or function or through the shown Gradle source-set setting. The supplied excerpt does not describe further behavior or limitations.

### Source excerpt

AI generated image Ditch redundant if-else boilerplate and awkward scope chaining with the newly introduced onTrue(), onFalse(), and ifOrNull() functions. Kotlin has always excelled at eliminating boilerplate. From concise data classes and standard scope functions (apply, also, let, takeIf) to smart casting, the language consistently seeks ways to make everyday idioms more expressive. Kotlin 2.5.0-Beta2 adds standard library functions that let us inspect a value before returning it, or return a nullable result based on that value. https://kotlinlang.org/docs/whatsnew-eap.html?utm_campaign=kotlin-releases&utm_content=2-5-0-beta2 Boolean.onTrue(action: () -> Unit): Boolean Boolean.onFalse(action: () -> Unit): Boolean ifOrNull(condition: Boolean, action: () -> T): T? Implementation Because these functions are introduced as experimental APIs in the standard library, we need to opt in to use them. File/Function Annotation OptIn(ExperimentalStdlibApi::class) Module-wide via Gradle config kotlin { sourceSets.all { languageSettings.optIn("kotlin.ExperimentalStdlibApi") } }onTrue() & onFalse() Both functions invoke a supplied block when the receiver matches the condition and return the original boolean unmodified. Example data class User(val id: String, val email: String) class AuthService() { // Before: fun authenticateLegacy(user: User, token: String): Boolean { val isValid = verifyToken(user.email, token) if (isValid) { "Auth.success" } else { "Auth.failure" } return isValid } // Now: @OptIn(ExperimentalStdlibApi::class) fun authenticate(user: User, token: String): Boolean = verifyToken(user.email, token) .onTrue { "Auth.success" } .onFalse { "Auth.failure" } }ifOrNull() When shaping API responses or DTOs, we may return one computed value if a flag is true and another if false. Traditionally, this looks like 👇 val phoneNumber = if (user.hasContactInfo) user.phoneNumber else nullThe New Way: ifOrNull() ifOrNull(condition) { //.. } lazily evaluates the lambda block only if

## What's fixed in IntelliJ IDEA 2026.3

DevFeed: [What's fixed in IntelliJ IDEA 2026.3](<https://devfeed.tech/articles/what-s-fixed-in-intellij-idea-2026-3-119021.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/idea/2026/11/whats-fixed-in-intellij-idea-2026-3/>)

Author: Dmitriy Smirnov

Published: 2026-11-05T08:44:25Z

Content type: release

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [IntelliJ IDEA](<https://devfeed.tech/topics/intellij-idea.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [intellij idea plugin](<https://devfeed.tech/topics/intellij-idea-plugin.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [2026-3](<https://devfeed.tech/tags/2026-3.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [code-intelligence](<https://devfeed.tech/tags/code-intelligence.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [idea](<https://devfeed.tech/tags/idea.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [intellij](<https://devfeed.tech/tags/intellij.md>), [intellij-idea](<https://devfeed.tech/tags/intellij-idea.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [performance](<https://devfeed.tech/tags/performance.md>), [reports](<https://devfeed.tech/tags/reports.md>), [usability](<https://devfeed.tech/tags/usability.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

IntelliJ IDEA 2026.3 reports over 1,000 bug fixes and over 300 performance fixes, with work focused on freezes, resource use, Java and Kotlin code intelligence, and core workflows. The article highlights fixes across project import, Spring, Scala, Markdown, Git, debugging, and build tools. JaCoCo is now the default coverage runner for new Java configurations; Maven-delegated builds now run `process-test-classes` by default. The debugger suggests a restart for Java and Kotlin edits that HotSwap cannot reload, while Spring scenarios retain prior behavior. Automatic error and UI-freeze reporting sends technical data after removing file paths, URLs, and usernames; reporting can be disabled in Settings. The release also adds plugin management changes and GitLab OAuth, and deprecates several Big Data Tools plugins while retaining support for Big Data Tools Core and Remote File Systems.

### Source excerpt

Welcome to an overview of the most important fixes and usability improvements in IntelliJ IDEA 2026.3. IntelliJ IDEA 2026.3 ships over 1,000 bug fixes and over 300 performance fixes. We focused on performance, Java and Kotlin code intelligence, and the core workflows that matter for both classic and agentic development. User reports and data shared [...]

## Let's Talk About Black October

DevFeed: [Let's Talk About Black October](<https://devfeed.tech/articles/let-s-talk-about-black-october-117811.md>)

Original publisher: [Read original article](<https://blog.gradle.org/lets-talk-about-black-october>)

Author: Laura Kassovic

Published: 2026-11-04T05:00:00Z

Content type: article

Language: en

Sources: [Gradle](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [black-october](<https://devfeed.tech/tags/black-october.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Black October was a cluster of unrelated disclosures, but the eMudhra certificate compromise exposed JVM builds because tested JDKs trusted forged chains and carry their own `cacerts` trust store. Gradle itself needed no patch; Gradle's CI blocked compromised certificates across JDKs, OS bundles, and machine images. The article says to update JDKs and verify the fix, identify the JDK and trust store used by builds and images, and enable dependency verification and locking. It also details a separate Brotli risk: `brotli4j` before 1.24.0 bundles vulnerable native code; locate it in project and build dependencies, then upgrade it or the supplying plugin. Dependency verification metadata should be reviewed because bootstrapping trusts current downloads. The article notes that GitHub-hosted Linux and macOS runners remained exposed at publication, while Windows rejected the forged chain.

### Source excerpt

For four days in October, our security channels read like the montage at the start of a disaster movie. Between October 19 and 22, 2026, so many serious disclosures went public that people started calling the whole month Black October. Black October is a media label, and a slightly misleading one, because it suggests a single attack or a single bug. It was a pile-up of unrelated vulnerabilities, several of which had been sitting in code for months or years, that happened to land in the same week. Most of it had nothing to do with Gradle, but one piece affects any build that runs on a JVM, which is every Gradle build ever. This post covers what happened, what it looked like from inside Gradle (including the places where we were exposed), and what we'd check before the next pile-up arrives. What actually happened during Black October? Here's the short tour: Disclosure What it was Why build engineers should care PHP2Shell Two remote code execution flaws in the PHP runtime (CVE-2026-109618 and CVE-2026-109619). Amazon's honeypots saw the first exploit attempt on October 17, and PHP shipped fixes on October 21. Not a JVM problem, but the cleanest example of the patch race. Node2Shell An out-of-bounds write in the Brotli C decoder (CVE-2026-111497), affecting Brotli 1.0.3 through 1.2.0. Node.js bundles it, and so do Java wrappers like brotli4j. Vulnerable native code can ride in on a dependency you never picked. eMudhra CA compromise Eight intermediate CA certificates whose private keys were generated so badly that anyone can recover them from the certificates. One of the keys was literally the number 4. They chain to roots your JDK trusts. Linux kernel list leak Unpatched kernel bugs posted to the public kernel mailing list instead of the private security list. Disclosure itself became a point of failure. LiteLLM on PyPI A malicious release (1.107.0) published through the project's own release pipeline with a credential stealer. It was live for about two hours. The build

## Java News Roundup: TornadoVM 8.0, JNoSQL, Endive, JReleaser, JBang, LangChain4j, Quarkus Almanac

DevFeed: [Java News Roundup: TornadoVM 8.0, JNoSQL, Endive, JReleaser, JBang, LangChain4j, Quarkus Almanac](<https://devfeed.tech/articles/java-news-roundup-tornadovm-8-0-jnosql-endive-jreleaser-jbang-langchain4j-quarkus-almanac-112551.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/java-news-roundup-oct26-2026/>)

Author: Michael Redlich

Published: 2026-11-02T17:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [releases](<https://devfeed.tech/topics/releases.md>), [TornadoVM](<https://devfeed.tech/topics/tornadovm.md>), [Hibernate](<https://devfeed.tech/topics/hibernate.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [langchain4j](<https://devfeed.tech/topics/langchain4j.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Project Leyden](<https://devfeed.tech/topics/project-leyden.md>), [jpa](<https://devfeed.tech/topics/jpa.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [beta](<https://devfeed.tech/tags/beta.md>), [development](<https://devfeed.tech/tags/development.md>), [eclipse-jnosql](<https://devfeed.tech/tags/eclipse-jnosql.md>), [endive](<https://devfeed.tech/tags/endive.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [hibernate](<https://devfeed.tech/tags/hibernate.md>), [hibernate-orm](<https://devfeed.tech/tags/hibernate-orm.md>), [hibernate-reactive](<https://devfeed.tech/tags/hibernate-reactive.md>), [java](<https://devfeed.tech/tags/java.md>), [java-news-roundup-oct26-2026](<https://devfeed.tech/tags/java-news-roundup-oct26-2026.md>), [jbang](<https://devfeed.tech/tags/jbang.md>), [jdk-28](<https://devfeed.tech/tags/jdk-28.md>), [jobrunr](<https://devfeed.tech/tags/jobrunr.md>), [jreleaser](<https://devfeed.tech/tags/jreleaser.md>), [langchain4j](<https://devfeed.tech/tags/langchain4j.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [news](<https://devfeed.tech/tags/news.md>), [news-roundup](<https://devfeed.tech/tags/news-roundup.md>), [october](<https://devfeed.tech/tags/october.md>), [point-releases](<https://devfeed.tech/tags/point-releases.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [tornadovm](<https://devfeed.tech/tags/tornadovm.md>)

### AI overview

The roundup reports TornadoVM 8.0.0's shift to a pure-Java compiler that targets CUDA C++, OpenCL C, and Metal Shading Language while retaining existing APIs and annotations. Other notable updates include JNoSQL 1.2.0's vector database integrations and temporal queries; JBang's move from SDKMan to mise-en-place for Windows support; and LangChain4j 1.23.0's Ollama decision model and confidence cascade planner. Hibernate's betas add association-level filtering and identifier generator configuration, while Hibernate Reactive adds a BOM and minimum-version checks. Gradle 9.9.0 RC adds incremental Kotlin DSL compilation and test filters. The new Quarkus Almanac compares configuration, dependencies, extensions, and jar APIs across releases back to 2018. The roundup also notes JDK 28 build updates, Endive and JReleaser features, and a JobRunr maintenance release.

### Source excerpt

This week's Java roundup for October 26th, 2026, features news highlighting: the GA release of TornadoVM 8.0; point releases of JNoSQL, Endive, JBang, JReleaser and LangChain4j; a maintenance release of JobRunr; beta releases of Hibernate ORM and Hibernate Reactive; and introducing the Quarkus Almanac. By Michael Redlich

## Side Quest: How Gradle Is Removing Ant

DevFeed: [Side Quest: How Gradle Is Removing Ant](<https://devfeed.tech/articles/side-quest-how-gradle-is-removing-ant-109457.md>)

Original publisher: [Read original article](<https://blog.gradle.org/side-quest-removing-ant>)

Author: Laura Kassovic

Published: 2026-10-29T04:00:00Z

Content type: article

Language: en

Sources: [Gradle](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Hackathon](<https://devfeed.tech/topics/hackathon.md>)

Tags: [built-in](<https://devfeed.tech/tags/built-in.md>), [cost](<https://devfeed.tech/tags/cost.md>), [days](<https://devfeed.tech/tags/days.md>), [deprecation](<https://devfeed.tech/tags/deprecation.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [fast](<https://devfeed.tech/tags/fast.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hackathon](<https://devfeed.tech/tags/hackathon.md>), [migration](<https://devfeed.tech/tags/migration.md>), [native](<https://devfeed.tech/tags/native.md>), [need](<https://devfeed.tech/tags/need.md>), [october](<https://devfeed.tech/tags/october.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

Gradle 9.9.0 deprecates its built-in Ant API, with removal and the end of Ant classes on build script classpaths planned for Gradle 10. Ant currently ships with every Gradle distribution; the article cites Configuration Cache incompatibility, Groovy coupling, and maintenance effort as costs. Builds that never call Ant or import its classes need no changes. Others can use Gradle equivalents, invoke tools directly, replace supported filters with `filter(Transformer)`, add Ant to build logic, or run Ant in a separate process. Migration details matter: Gradle `Copy` copies files regardless of destination timestamps, `Exec` fails on nonzero exit by default, and declared task inputs and outputs enable caching. The proposed filter replacement works line by line and has limits for multiline tokens and filters such as `HeadFilter` or `TailFilter`. Gradle's own Ant-backed PMD, CodeNarc, and Checkstyle plugins are separate cleanup work, not tied to Gradle 10.

### Source excerpt

In October, the Gradle team spent a week together in Istanbul, and one of those days was a hackathon. One group picked a side quest with a deceptively short description: remove Ant from the Gradle distribution. Then we looked at gradle/gradle and we counted. Ant turned out to back 58 imports across 12 different Gradle features. So "remove Ant" became a deprecation in Gradle 9.9.0, a removal planned for Gradle 10, and a long new section in our upgrade guide. TL;DR: Gradle 9.9.0 deprecates the built-in Ant integration, and we plan to remove it in Gradle 10. Gradle 10 also stops putting Ant classes on your build script classpath. Why: a modern Gradle build shouldn't need Ant, and carrying it holds Gradle back. If your build calls ant, the migration section covers how to move off it. Gradle's own internal Ant usage, like the PMD, CodeNarc, and Checkstyle plugins, goes away separately and isn't tied to Gradle 10. Why is Gradle removing Ant? Gradle's Ant integration was largely about ease of migration. If your build was in Ant, you could bring it into Gradle and move it over piece by piece. That isn't really a concern anymore. We've asked whether Gradle should keep its Ant support for years, and this deprecation is our answer. A proper Gradle build shouldn't need Ant for anything, and if we spot Ant in a build today, we recommend moving off it. Where does Ant fit in "fast, flexible, scalable, comprehensible"? It doesn't. We judge features against what Gradle is supposed to be, and native Ant integration isn't on that list. Our job is to give you a platform where you can integrate Ant if you need it. The migration paths below do exactly that. What does keeping Ant cost? Ant ships in every Gradle distribution, whether your build uses it or not. It sits in the Gradle API JAR and on your build script classpath. When you run gradle --version, Gradle prints the Ant version next to its own: ------------------------------------------------------------ Gradle 9.8.2 ---------------

## Migrating A Flutter Project to Built In Kotlin

DevFeed: [Migrating A Flutter Project to Built In Kotlin](<https://devfeed.tech/articles/migrating-a-flutter-project-to-built-in-kotlin-105647.md>)

Original publisher: [Read original article](<https://medium.com/flutter-community/migrating-a-flutter-project-to-built-in-kotlin-e0e41f2ea11a?source=rss----86fb29d7cc6a---4>)

Author: tomerpacific

Published: 2026-10-28T15:42:03Z

Content type: tutorial

Language: en

Sources: [Flutter Community](<https://devfeed.tech/sources/flutter-community-medium.md>)

Topics: [Flutter](<https://devfeed.tech/topics/flutter.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [built-in](<https://devfeed.tech/tags/built-in.md>), [dart](<https://devfeed.tech/tags/dart.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>)

### AI overview

Migrating a Flutter project to built-in Kotlin requires Flutter 3.44 or later and, for AGP 9 support, updates to the Android build configuration. The article says to use Flutter's stable channel, upgrade Flutter, set the minimum Flutter version in pubspec.yaml, remove the applied Kotlin Android plugin from the app build file, replace kotlinOptions with the Kotlin compilerOptions block, and update gradle.properties. Android Studio Otter 3 is identified as the first version supporting AGP 9. Dependencies must also support built-in Kotlin; otherwise, the author recommends replacing them or delaying migration. A pure Dart script can inspect a project and propose edits, but changes require approval, manual steps remain, and dependency blockers may persist. Its sample report also cautions that duplicate settings.gradle files can make findings misleading.

### Source excerpt

🙌 TL;DR I created a dart script to automatically migrate your Flutter project with ease. You can find it at the bottom of this article. If your application or plugin supports Flutter version >= 3.44, then you might consider migrating it to use Built In Kotlin support. This is needed in order to support Android Gradle Plugin (AGP) versions >= 9. If you are not supporting Flutter version >= 3.44 or if your project is not currently using AGP >= 9, you don't need to do this right now, but you might want to consider it. I have undergone this migration process with one of my applications, and would like to share the process I had to go through, so you may have an easier going though it. ✋ If you have a Flutter plugin that is a pure Dart plugin (meaning no native Android code), then you don't need to do anything regarding the migration and you can leave it as is.Setting up Flutter >= 3.44 The first thing you need to do in order to migrate your application/plugin is to make sure you are on a Flutter version that supports it. That means, to upgrade your local Flutter version to at least 3.44. Before you upgrade the version, make sure you are on the stable channel in Flutter. You can do so by opening up a terminal and typing: flutter channel If the output shows you that you are on the stable channel, you can proceed to upgrade by typing: flutter upgrade This will upgrade your Flutter version to the latest one in the stable channel. After doing this, we need to also declare in our pubspec.yaml file what our minimum supported Flutter version is: environment: sdk: ^3.2.0 flutter: '>=3.44.0'Upgrading AGP >= 9 (the manual approach) To upgrade the Android Gradle Plugin version to be >= 9, you need to open the android folder of your Flutter project. Make sure you have at least Android Studio Otter 3 since that is the first version that supports AGP 9. Once you have opened the project, you can use the AGP Upgrade Assistant under the Tools menu option. Now, there are several changes you need

## Improving the Smoothness of Android Compose Screens

DevFeed: [Improving the Smoothness of Android Compose Screens](<https://devfeed.tech/articles/improving-the-smoothness-of-android-compose-screens-100955.md>)

Original publisher: [Read original article](<https://proandroiddev.com/improving-the-smoothness-of-android-compose-screens-47607da631c8?source=rss----c72404660798---4>)

Author: rayford

Published: 2026-10-26T13:33:21Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Compose Compiler](<https://devfeed.tech/topics/compose-compiler.md>), [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Android](<https://devfeed.tech/topics/android.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-compose](<https://devfeed.tech/tags/android-compose.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [compose-performance](<https://devfeed.tech/tags/compose-performance.md>), [ide](<https://devfeed.tech/tags/ide.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [monitoring-and-evaluation](<https://devfeed.tech/tags/monitoring-and-evaluation.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [performance](<https://devfeed.tech/tags/performance.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [recomposition](<https://devfeed.tech/tags/recomposition.md>), [rendering](<https://devfeed.tech/tags/rendering.md>), [screen](<https://devfeed.tech/tags/screen.md>), [skip](<https://devfeed.tech/tags/skip.md>), [stable](<https://devfeed.tech/tags/stable.md>), [state](<https://devfeed.tech/tags/state.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Compose screen performance depends on how often recomposition is triggered, parameter stability, and where state changes occur in the UI hierarchy. Frequent state changes are identified as a common source of excessive recomposition; declaring unchanged values as `val` can help avoid unnecessary updates, and IDE plugins can expose composable parameter stability. To find changing values, Rebugger compares state and parameters during recomposition and logs differences. The excerpt then describes Compose Monitor, which injects monitoring into annotated composables at compile time: its Android ASM approach uses two bytecode passes but depends on compiler-generated patterns that may change and supports only Android. Its proposed Kotlin compiler IR approach inserts monitoring calls before function exits and is intended to support Kotlin versions 2.0 and later, with platform-specific compilation backends. The excerpt notes that IR plugin APIs differ across Kotlin versions.

### Source excerpt

As Android development moves from the legacy View system to Jetpack Compose, the more modern Compose approach brings a very different development experience. The two also differ substantially in their tooling and performance-tracking workflows. In addition to frame-rate monitoring, the View system commonly relies on ANR reports to identify problematic stack traces. Compose, however, updates the UI in response to data changes, so an ANR stack trace may not point to the code responsible for the issue. Factors That Affect Compose Screen Performance Compose keeps screen state in memory. When that state changes, it triggers recomposition of the corresponding parts of the UI. The following factors affect rendering performance: How frequently recomposition is triggered Whether method parameters are stable The UI hierarchy in which the state change is triggered Stability is one of the factors Compose uses to decide whether it can skip recomposition. In day-to-day development, declaring values that do not change as val can help avoid unnecessary state updates and recompositions. Open-source IDE plugins can also show whether parameters of composable functions are stable directly in the editor. Compose Stability Analyzer The most common cause of Compose performance issues is frequent state changes that trigger excessive recompositions. Identifying the frequently changing state is the key to finding the root cause. Monitoring Compose-Triggered UI Updates One approach is to collect all state and parameters, compare their values whenever a composable function recomposes, and print the differences to logcat. Tools such as Rebugger already provide this capability, with an IDE plugin that can add the monitoring code. GitHub - theapache64/rebugger: A simple Compose Multiplatform library designed to print the reason for recomposition in your console/Logcat window." Minimizing Intrusion by Injecting Monitoring Code Automatically Most of the time, state changes do not need to be monitor

## A Java IDE in Your Browser, With Your Files in Your Browser

DevFeed: [A Java IDE in Your Browser, With Your Files in Your Browser](<https://devfeed.tech/articles/a-java-ide-in-your-browser-with-your-files-in-your-browser-94005.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/not-a-cloud-ide/>)

Author: Shai Almog

Published: 2026-10-22T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [backend](<https://devfeed.tech/tags/backend.md>), [backup](<https://devfeed.tech/tags/backup.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-ide](<https://devfeed.tech/tags/browser-ide.md>), [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [button](<https://devfeed.tech/tags/button.md>), [compile](<https://devfeed.tech/tags/compile.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [export](<https://devfeed.tech/tags/export.md>), [files](<https://devfeed.tech/tags/files.md>), [ide](<https://devfeed.tech/tags/ide.md>), [java](<https://devfeed.tech/tags/java.md>), [preview](<https://devfeed.tech/tags/preview.md>), [project](<https://devfeed.tech/tags/project.md>), [run](<https://devfeed.tech/tags/run.md>), [zip](<https://devfeed.tech/tags/zip.md>)

### AI overview

The experimental Codename One browser IDE lets you edit a multi-file Java project, compile it for preview, and run the app in the browser. A starter project is ready to run; the article demonstrates replacing its screen with a counter. Editing and preview run in the browser, while cloud builds are an explicit handoff to Codename One's build service. Project files stay in that browser's storage with no cloud backup, so Download ZIP is the way to back them up or continue with Maven or Gradle locally. The IDE offers compiler errors, completion, hover information, and source navigation, but not a full Java language server or IntelliJ refactoring. Preview supports a defined subset of dependencies and build behavior; backend projects can be edited and exported, but only the client runs in full-stack preview. Device behavior still needs checking on real targets.

### Source excerpt

Try the experimental Codename One browser IDE: edit a project, compile Java and run a preview locally in the page. Export a ZIP when you want to continue on your desktop.

## The Sentry Android SDK is now 20-30% faster!

DevFeed: [The Sentry Android SDK is now 20-30% faster!](<https://devfeed.tech/articles/the-sentry-android-sdk-is-now-20-30-faster-91146.md>)

Original publisher: [Read original article](<https://blog.sentry.io/android-sdk-faster-startup/>)

Author: Nelson Osacky

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Sentry](<https://devfeed.tech/sources/sentry-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [app startup](<https://devfeed.tech/topics/app-startup.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Macrobenchmark](<https://devfeed.tech/topics/macrobenchmark.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [build](<https://devfeed.tech/tags/build.md>), [faster](<https://devfeed.tech/tags/faster.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [sentry](<https://devfeed.tech/tags/sentry.md>), [startup](<https://devfeed.tech/tags/startup.md>), [thread](<https://devfeed.tech/tags/thread.md>), [thread-pools](<https://devfeed.tech/tags/thread-pools.md>), [time](<https://devfeed.tech/tags/time.md>)

### AI overview

Sentry reports that Android SDK initialization measured by `SentryAndroid.init` was 20-30% faster in version 8.54.0 than 8.43.0. The measurement used a synthetic app and does not represent total app startup; customer benchmarks reportedly found similar results, though real-world outcomes vary. Changes included writing manifest options into bytecode at build time so the SDK can skip manifest parsing (6.5% benchmark improvement), replacing `java.net.URI` DSN parsing with a custom parser (up to 6 ms reduced to 1 µs in the benchmark), and reusing shared executor pools instead of creating one-off threads, reducing SDK heap size by 3 MB. The team benchmarked changes with Android Macrobenchmark. To get the improvements, the excerpt specifies Android SDK 8.54.0 or later and Sentry Android Gradle Plugin 6.20.0 or later.

### Source excerpt

Sentry Android SDK 8.54.0 initializes 20-30% faster. See how build-time options, faster DSN parsing, and shared thread pools cut startup cost.

## The Evolution of Statics: Say Goodbye to Kotlin Companion Objects?

DevFeed: [The Evolution of Statics: Say Goodbye to Kotlin Companion Objects?](<https://devfeed.tech/articles/the-evolution-of-statics-say-goodbye-to-kotlin-companion-objects-85014.md>)

Original publisher: [Read original article](<https://proandroiddev.com/the-evolution-of-statics-say-goodbye-to-kotlin-companion-objects-dbe625b92896?source=rss-711ab22c5c77------2>)

Author: Nav Singh

Published: 2026-10-11T02:28:53Z

Content type: tutorial

Language: en

Sources: [Nav Singh](<https://devfeed.tech/sources/stories-by-nav-singh-on-medium.md>)

Topics: [extension property](<https://devfeed.tech/topics/extension-property.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [class](<https://devfeed.tech/topics/class.md>), [Object-oriented programming (OOP)](<https://devfeed.tech/topics/oop.md>), [interface implementation](<https://devfeed.tech/topics/interface-implementation.md>)

Tags: [androiddev](<https://devfeed.tech/tags/androiddev.md>), [block](<https://devfeed.tech/tags/block.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [class](<https://devfeed.tech/tags/class.md>), [classes](<https://devfeed.tech/tags/classes.md>), [companion](<https://devfeed.tech/tags/companion.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cross](<https://devfeed.tech/tags/cross.md>), [extension](<https://devfeed.tech/tags/extension.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [factory](<https://devfeed.tech/tags/factory.md>), [implement](<https://devfeed.tech/tags/implement.md>), [interface](<https://devfeed.tech/tags/interface.md>), [interop](<https://devfeed.tech/tags/interop.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [memory](<https://devfeed.tech/tags/memory.md>), [module](<https://devfeed.tech/tags/module.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [static](<https://devfeed.tech/tags/static.md>)

### AI overview

The excerpt presents Kotlin 2.5.0-Beta1 companion blocks and companion extensions as experimental alternatives to companion objects. Companion blocks compile members directly as static bytecode on the parent class, allowing Java calls such as `User.createDefault()` without `@JvmStatic`; unlike companion objects, they cannot implement interfaces because they are not objects. Companion extensions add static-like members to a type from outside its declaration, with examples including third-party factories, configuration initializers, and domain constants; regular extension functions instead operate on instances. Trying the preview requires the JetBrains Bootstrap Repository, Kotlin 2.5.0-Beta1, JVM toolchain 21, and the `-Xcompanion-blocks` and `-Xcompanion-blocks-and-extensions` compiler flags.

### Source excerpt

AI generated image For years, we used companion object to group class-level members (constants, factory methods). However, companion objects are actual object singletons under the hood. This introduces memory overhead and causes friction when interoperating with Java (requiring @JvmStaticannotations). data class User(val name: String, val age: Int) { companion object { @JvmStatic fun createDefault(): User = User("Guest", 18) } }AI generated imageKotlin 2.5 introduces companion blocks and companion extensions: Companion Blocks: Drop the object keyword. On the JVM, they compile down directly into high-performance native static members. Companion Extensions: Let us attach new static-like methods or properties to any class from the outside, even classes inside external dependencies or standard Java SDKs we don't control. Companion Blocks vs. Companion Objects Under the Hood: A companion object creates a nested singleton subclass instantiation. A companion block compiles directly to static bytecode members on the parent class. Interface Limitation: Companion objects are still required if static-scoped layer needs to implement an interface. Companion blocks cannot implement interfaces because they are not real objects. Java Interop: Java code can call companion block members directly via User.createDefault(). Companion objects still require User.Companion.createDefault() unless decorated with @JvmStatic. Companion Extensions vs. Regular Extension Functions Call Site: Regular extensions require an existing instance (userInstance.isValid()). Companion extensions are invoked statically on the type itself (User.systemAdmin()). Use Cases: Regular extensions add instance operations (mapping, filtering, etc.). Companion extensions serve as third-party factories, cross-module configuration initializers, or domain constants. Implementation🛠 Setting Up the project Companion Blocks and Extensions are arriving as experimental features in Kotlin 2.5.0-Beta1 To try this out today, we

## How I Built Free and Full Build Flavors for Android in my KMP codebase

DevFeed: [How I Built Free and Full Build Flavors for Android in my KMP codebase](<https://devfeed.tech/articles/how-i-built-free-and-full-build-flavors-for-android-in-my-kmp-codebase-84566.md>)

Original publisher: [Read original article](<https://proandroiddev.com/how-i-built-free-and-full-build-flavors-for-android-in-my-kmp-codebase-511bffdcc28c?source=rss----c72404660798---4>)

Author: Avik Sharma Chowdhury

Published: 2026-10-10T17:17:07Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [app](<https://devfeed.tech/tags/app.md>), [auth](<https://devfeed.tech/tags/auth.md>), [billing](<https://devfeed.tech/tags/billing.md>), [build](<https://devfeed.tech/tags/build.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [flavors](<https://devfeed.tech/tags/flavors.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The tutorial explains how an Android app built with Kotlin Multiplatform uses Gradle product flavors to create free and full variants from one codebase. Flavor-specific dependencies keep authentication, sync and payment modules, SDKs and billing permission out of the free build, while shared code uses interfaces and flavor-specific implementations. A GitHub Actions CI check guards against full-only SDKs returning to the free release build.

### Source excerpt

How I Built Free and Full Build Flavors for Android in My KMP CodebasePart 3 of my KMP series: how Android product flavors let the free version of my app leave the sign-in, sync and payment code out of the build List: Building an Exam Prep App with Kotlin Multiplatform | Curated by Avik Sharma Chowdhury | Medium In Part 1, I shared how my plan changed after completing the closed testing with MVP. I decided to launch the app for free and keep the paid features (sign-in, cloud sync and a premium subscription) ready for later. In Part 2, I walked through how the project is organized. This part is about how one codebase builds both versions: a free app with only the core features, and a full app with everything. I'll cover product flavors, how the free app leaves the premium features out, and how the shared code works with either version without knowing which one it's in. One note before we start: product flavors are an Android feature, and everything in this part is about the Android app. On iOS, I plan to release the full version, so the iOS code simply includes all the features. Why Two Builds? My first attempt was introducing a feature flag that hid the premium features. The free version still included the Auth and Payment SDKs and still asked for the billing permission, even though no one can buy anything. I wanted the free app to contain only what it uses. That meant building two different apps from the same code. Product Flavors A product flavor is Android's way of building different versions of an app from one codebase. You define flavors in Gradle, and each flavor can have its own code, resources and dependencies. https://medium.com/media/0fdcaa2efa27e84b78270d2d428385d9/href The flavors are grouped into two dimensions: environment (dev / prod): a development version and a release version. The dev build has a different app ID, so both can be installed on the same phone. distribution (free / full): which features the app includes. The free flavor has only the co

## Java and Kotlin by IntelliJ IDEA: The LSP-Based Extension Reaches Release Candidate

DevFeed: [Java and Kotlin by IntelliJ IDEA: The LSP-Based Extension Reaches Release Candidate](<https://devfeed.tech/articles/java-and-kotlin-by-intellij-idea-the-lsp-based-extension-reaches-release-candidate-65705.md>)

Original publisher: [Read original article](<https://blog.jetbrains.com/idea/2026/10/java-and-kotlin-by-intellij-idea-the-lsp-based-extension-reaches-release-candidate/>)

Author: Maria Kosukhina

Published: 2026-10-06T09:54:39Z

Content type: release

Language: en

Sources: [JetBrains](<https://devfeed.tech/sources/the-jetbrains-blog.md>)

Topics: [VS Code Extension](<https://devfeed.tech/topics/vscode-extension.md>), [Visual Studio Code](<https://devfeed.tech/topics/visual-studio-code.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [code-completion](<https://devfeed.tech/tags/code-completion.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [java](<https://devfeed.tech/tags/java.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [news](<https://devfeed.tech/tags/news.md>), [release](<https://devfeed.tech/tags/release.md>), [vs-code](<https://devfeed.tech/tags/vs-code.md>)

### AI overview

Java and Kotlin by IntelliJ IDEA, an LSP-based extension for VS Code and compatible editors, has reached release candidate status. It brings IntelliJ IDEA language features such as code completion, navigation, analysis, refactoring, debugging, build tool support, and test running to those editors. The release candidate is available through the Early Access Program for 30 days; the stable release will require an IntelliJ IDEA Ultimate subscription after a 30-day trial.

### Source excerpt

Two months ago, we announced the preview of Java and Kotlin by IntelliJ IDEA - an LSP-based extension that brings IntelliJ IDEA's Java and Kotlin intelligence to third-party editors, starting with VS Code and its forks, such as Cursor. This was our first step towards bringing IntelliJ IDEA's Java and Kotlin intelligence beyond the IDE, [...]

## Do You Prefer Gradle?

DevFeed: [Do You Prefer Gradle?](<https://devfeed.tech/articles/do-you-prefer-gradle-64651.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/gradle-smaller-projects/>)

Author: Shai Almog

Published: 2026-10-05T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [gradle-plugin](<https://devfeed.tech/topics/gradle-plugin.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [build-tool](<https://devfeed.tech/tags/build-tool.md>), [development](<https://devfeed.tech/tags/development.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [maven](<https://devfeed.tech/tags/maven.md>), [modules](<https://devfeed.tech/tags/modules.md>)

### AI overview

Codename One added optional Gradle support to produce smaller project layouts, create standalone Java backends, and reuse the build engine shared with Maven. The article describes the supported Gradle workflows, conversion from Maven, and limitations, including Java 17 requirements and features that still lack Gradle equivalents. It also explains an opt-in Gradle 9 path for Android builds and advises testing actual native dependencies and generated projects.

### Source excerpt

Optional Gradle projects remove empty platform modules, support standalone backends, and use the same build engine as Maven.

## Kotlin Multiplatform iOS build times: what's actually driving the cost

DevFeed: [Kotlin Multiplatform iOS build times: what's actually driving the cost](<https://devfeed.tech/articles/kotlin-multiplatform-ios-build-times-what-s-actually-driving-the-cost-64358.md>)

Original publisher: [Read original article](<https://johnoreilly.dev/posts/kmp-ios-build-times/>)

Published: 2026-10-02T23:00:00Z

Content type: article

Language: en

Sources: [John O'Reilly](<https://devfeed.tech/sources/john-o-reilly.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [build times](<https://devfeed.tech/topics/build-times.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [kmp](<https://devfeed.tech/tags/kmp.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>)

### AI overview

The article benchmarks Kotlin Multiplatform iOS build times against Swift, examining Kotlin versions, framework setup, exported API size, and Swift export. It finds that limiting the API exposed to Swift can substantially reduce incremental build times, while Kotlin version changes have little effect in these tests. Swift export is slower than the Objective-C-based framework in the measured scenarios. The results use generated code on one machine, so real-world savings depend on how much code can remain internal.

### Source excerpt

A recent article, The Hidden Cost Behind Kotlin Multiplatform on iOS, looked at what KMP does to the iOS edit/build/run feedback loop. It's a good question to ask and the article also comes with a benchmark harness (kmp-ios-benchmark) that compares a Swift-only setup against an equivalent KMP one, using generated code across clean, incremental, public API change, multi-module and release builds. The headline numbers were that a single internal change rebuilt in 3.19s for Swift vs 10.36s for KMP, and that the gap grew with module size (KMP adding ~4.2x more time per 100 files than Swift).

## Java Weekly, Issue 666

DevFeed: [Java Weekly, Issue 666](<https://devfeed.tech/articles/java-weekly-issue-666-63816.md>)

Original publisher: [Read original article](<https://www.baeldung.com/java-weekly-666>)

Author: baeldung

Published: 2026-10-02T12:07:00Z

Content type: article

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [JDK Flight Recorder](<https://devfeed.tech/topics/jdk-flight-recorder.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Project Valhalla](<https://devfeed.tech/topics/project-valhalla.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [java](<https://devfeed.tech/tags/java.md>), [no-ads](<https://devfeed.tech/tags/no-ads.md>), [no-after-post](<https://devfeed.tech/tags/no-after-post.md>), [no-before-post](<https://devfeed.tech/tags/no-before-post.md>), [no-optins](<https://devfeed.tech/tags/no-optins.md>), [performance](<https://devfeed.tech/tags/performance.md>), [weekly](<https://devfeed.tech/tags/weekly.md>), [weekly-review](<https://devfeed.tech/tags/weekly-review.md>), [weekly-review-no-ads-no-after-post-no-before-post-no-optins](<https://devfeed.tech/tags/weekly-review-no-ads-no-after-post-no-before-post-no-optins.md>)

### AI overview

This issue of Java Weekly collects Java news, releases, and articles. It highlights JDK 27 performance improvements, JVM benchmarking pitfalls, Java workflow execution, cloud identity and container sizing, alongside framework and tooling updates.

### Source excerpt

Monoliths, Java 28 and performance. A good week. The post Java Weekly, Issue 666 first appeared on Baeldung.

## Modular Jetpack Compose: Don't Leave Your Architecture to Code Review

DevFeed: [Modular Jetpack Compose: Don't Leave Your Architecture to Code Review](<https://devfeed.tech/articles/modular-jetpack-compose-don-t-leave-your-architecture-to-code-review-63717.md>)

Original publisher: [Read original article](<https://proandroiddev.com/modular-jetpack-compose-dont-leave-your-architecture-to-code-review-67b1b916097c?source=rss----c72404660798---4>)

Author: Kanan Yusubov

Published: 2026-10-02T04:56:58Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [decoupling](<https://devfeed.tech/topics/decoupling.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-architecture](<https://devfeed.tech/tags/android-architecture.md>), [api](<https://devfeed.tech/tags/api.md>), [api-impl](<https://devfeed.tech/tags/api-impl.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [build](<https://devfeed.tech/tags/build.md>), [ci](<https://devfeed.tech/tags/ci.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [compose](<https://devfeed.tech/tags/compose.md>), [core](<https://devfeed.tech/tags/core.md>), [counter](<https://devfeed.tech/tags/counter.md>), [failure](<https://devfeed.tech/tags/failure.md>), [feature](<https://devfeed.tech/tags/feature.md>), [features](<https://devfeed.tech/tags/features.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [internals](<https://devfeed.tech/tags/internals.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [koin](<https://devfeed.tech/tags/koin.md>), [ktor](<https://devfeed.tech/tags/ktor.md>), [mobile-design-system](<https://devfeed.tech/tags/mobile-design-system.md>), [modular](<https://devfeed.tech/tags/modular.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>)

### AI overview

The article proposes enforcing modular Jetpack Compose architecture through Gradle and Kotlin rather than relying on review conventions. Each capability has an -api contract and an -impl module, with only the app allowed to depend on implementations; a shared Gradle guard checks all project dependency configurations. Kotlin internal visibility hides implementation details, while feature launchers expose routes without exposing route classes. Koin's compiler plugin checks dependency definitions at build time, and sealed result and failure types require exhaustive handling; cancellation is rethrown. A CI source check catches unregistered features and routes that compile-time checks miss, while a generator creates new feature wiring. The approach adds modules and navigation indirection; the author suggests it may suit apps with roughly ten features or multiple teams, while smaller apps may be fine with one module and discipline.

### Source excerpt

Every Android architecture diagram looks clean on day one. Features in boxes, arrows pointing down, a note in the README saying "features must not depend on each other." Then a deadline arrives. Someone needs the user's avatar on the checkout screen, the profile feature already has a UserRepository, and it's one import away. The build is green, the review is busy, and the arrow now points sideways. Six months later nobody can change the profile feature without breaking checkout. Folders and naming conventions describe an architecture. They don't enforce it. A rule that only lives in a README is a suggestion. This article takes six rules a modular Compose app usually lives by, and moves each one out of the README and into the build: Only the app may depend on an implementation. Enforced by a Gradle check. A module's internals stay private. Enforced by Kotlin's internal. Only a feature may build its own routes. Enforced by internal routes and launchers. Every dependency has a definition. Enforced by Koin's compiler plugin. Every failure is handled. Enforced by sealed types. Every feature and route is registered. Enforced by a source check that runs in CI. Where a rule can't be enforced, the last section makes the right way the easy way instead. The shape: every capability is two modules Each capability becomes a pair of Gradle modules: -api says what the capability can do. Interfaces only. -impl says how. Screens, view models, repositories, DTOs, wiring. app/ the only module that sees implementations features/ posts/posts-api PostsApi, PostsLauncher posts/posts-impl screens, view models, data, Koin module counter/counter-api counter/counter-impl depends on posts-api, never posts-impl core/ designsystem/ tokens, theme, components statemanager/ AppStateViewModel router/router-api | impl Navigation 3 network/network-api | impl Ktor logger/logger-api | impl Kermit Dependencies only point down: app -> features -> core. Features reach each other only through an -api. When che

## Agent Skills for Gradle Best Practices and Wrapper Upgrades

DevFeed: [Agent Skills for Gradle Best Practices and Wrapper Upgrades](<https://devfeed.tech/articles/agent-skills-for-gradle-best-practices-and-wrapper-upgrades-63458.md>)

Original publisher: [Read original article](<https://blog.gradle.org/introducing-gradle-skills>)

Author: Laura Kassovic

Published: 2026-09-30T04:00:00Z

Content type: article

Language: en

Sources: [Gradle](<https://devfeed.tech/sources/the-gradle-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [hardened ai agent skills](<https://devfeed.tech/topics/hardened-ai-agent-skills.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agents](<https://devfeed.tech/tags/agents.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [skills](<https://devfeed.tech/tags/skills.md>)

### AI overview

Gradle has released an official agent plugin with skills for auditing builds against Gradle best practices and upgrading Gradle wrappers. The article describes their workflows and evaluations, reporting improved results across tested models, including better wrapper upgrade checks and rollback behavior.

### Source excerpt

In August, we told you Gradle was going agentic. Today, we're shipping an official plugin that contains the first two Gradle skills. Version 1.0.0 is a starting point, and we have a lot more already in progress. TL;DR: We shipped two skills: gradle-best-practices and gradle-wrapper-upgrade. Install the gradle-skills agent plugin to get all skills and new ones we add later. We tested each skill on seven models from five vendors across three agent harnesses. Agents do better with the gradle-best-practices and gradle-wrapper-upgrade skills than without: cheaper models approached frontier-model results, and four models passed every upgrade check. Next up: A patch for these skills, new skills, and agent-friendly documentation. Quick refresher if you missed the first post. Agents are now Gradle users we have to design for, right alongside the person at the keyboard. A skill is a small package of instructions that teaches an agent to do one job well, so the agent follows a known procedure instead of guessing from whatever it half-remembers. What did we ship? We shipped a plugin containing two skills, located at github.com/gradle/gradle-skills: Skill What it does Ask it to... gradle-best-practices Audits your build against the official best practices, writes a prioritized report, and proposes fixes "Check my build" or "Apply best practices to my build" gradle-wrapper-upgrade Upgrades an existing Gradle wrapper, pins the checksum, verifies the result, and rolls back if the build no longer configures successfully "Upgrade the Gradle wrapper" or "How do I upgrade the wrapper?" How do I install the skills? We recommend installing our plugin, which gets you all of the skills now and every skill we add later. For example, in Claude Code: /plugin marketplace add gradle/gradle-skills /plugin install gradle-skills@gradle-skills You can also install through skills.sh, which covers Claude Code, Codex, Gemini, Cursor, and any other agent that reads the Agent Skills format: npx skills add

## Introduction to FitNesse - An Acceptance Testing Framework

DevFeed: [Introduction to FitNesse - An Acceptance Testing Framework](<https://devfeed.tech/articles/introduction-to-fitnesse-an-acceptance-testing-framework-58466.md>)

Original publisher: [Read original article](<https://www.baeldung.com/java-fitnesse-acceptance-testing-framework>)

Author: Olayemi Michael

Published: 2026-09-23T06:58:59Z

Content type: tutorial

Language: en

Sources: [Baeldung](<https://devfeed.tech/sources/baeldung.md>)

Topics: [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [Java](<https://devfeed.tech/topics/java.md>), [test](<https://devfeed.tech/topics/test.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Wiki](<https://devfeed.tech/topics/wiki.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Web](<https://devfeed.tech/topics/web.md>)

Tags: [acceptance](<https://devfeed.tech/tags/acceptance.md>), [framework](<https://devfeed.tech/tags/framework.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [java](<https://devfeed.tech/tags/java.md>), [let](<https://devfeed.tech/tags/let.md>), [maven](<https://devfeed.tech/tags/maven.md>), [programming](<https://devfeed.tech/tags/programming.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

This tutorial explains how to use FitNesse for acceptance testing of Java applications. It covers FitNesse's wiki-based interface and syntax, the Fit and Slim test systems, project setup with Maven or Gradle, and a banking application example using fixture classes.

### Source excerpt

Learn how to use FitNesse to write an acceptance test for your Java application. The post Introduction to FitNesse - An Acceptance Testing Framework first appeared on Baeldung.

## Gradle dependency drift can cause runtime crashes in KMP projects

DevFeed: [Gradle dependency drift can cause runtime crashes in KMP projects](<https://devfeed.tech/articles/runtime-crashes-hiding-in-your-gradle-files-nacho-carrion-55070.md>)

Original publisher: [Read original article](<https://touchlab.co/gradle-transitive-dependency-resolution>)

Published: 2026-09-18T18:00:00Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Gradle](<https://devfeed.tech/topics/gradle.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>)

Tags: [bug](<https://devfeed.tech/tags/bug.md>), [build](<https://devfeed.tech/tags/build.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [error](<https://devfeed.tech/tags/error.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-native](<https://devfeed.tech/tags/kotlin-native.md>), [transitive-dependencies](<https://devfeed.tech/tags/transitive-dependencies.md>)

### AI overview

The article explains how dependency version drift in Kotlin Multiplatform projects can pass compilation and release checks but cause runtime crashes, especially on iOS. It examines mismatched kotlinx-datetime versions and Gradle's newest-wins conflict resolution.

### Source excerpt

How transitive dependencies get out of sync and the Kotlin/Native change which makes it worse.

## Starting Android at Khan Academy

DevFeed: [Starting Android at Khan Academy](<https://devfeed.tech/articles/starting-android-at-khan-academy-27408.md>)

Original publisher: [Read original article](<http://engineering.khanacademy.org/posts/starting-android.htm>)

Author: Khan Academy

Published: 2016-02-29T23:00:00Z

Content type: article

Language: en

Sources: [Khan Academy](<https://devfeed.tech/sources/khan-academy.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [APK](<https://devfeed.tech/topics/apk.md>), [Picasso](<https://devfeed.tech/topics/picasso.md>)

Tags: [2015](<https://devfeed.tech/tags/2015.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [android](<https://devfeed.tech/tags/android.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code-sharing](<https://devfeed.tech/tags/code-sharing.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [core](<https://devfeed.tech/tags/core.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [design](<https://devfeed.tech/tags/design.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [developing](<https://devfeed.tech/tags/developing.md>), [development](<https://devfeed.tech/tags/development.md>), [device](<https://devfeed.tech/tags/device.md>), [download](<https://devfeed.tech/tags/download.md>), [education](<https://devfeed.tech/tags/education.md>), [employees](<https://devfeed.tech/tags/employees.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [environments](<https://devfeed.tech/tags/environments.md>), [journey](<https://devfeed.tech/tags/journey.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

Khan Academy's first Android app, launched in August 2015, used an Android-independent core module for data work and an app module for Android-specific presentation and changes. Running core tests on a vanilla JVM made them faster and avoided emulator maintenance; the team reports 1,290 tests running in about three seconds and used CI for compatibility checks. The modular setup added some build complexity. The team adopted Support Library components, Retrofit, and Picasso; used Stetho with OkHttp for on-device network debugging, a custom command-line DumperPlugin, and Triple-T's Gradle plugin for Play Store uploads. Nightly CI builds from master went to an internal alpha channel, with Git tags tracking version codes. UI testing and deployment remained slow, and the team had not found a satisfactory mobile code-sharing approach. It was exploring cross-platform sharing and offline access; those were ongoing efforts, not reported outcomes.

### Source excerpt

By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more

[Next page](<https://devfeed.tech/topics/gradle.md?cursor=WyIyMDI2LTA5LTE2VDA5OjQ5OjUzLjE3Mzg0NiswMDowMCIsICIzZmMzY2UyZi03YzM5LTQyYTItYmUxNC03NmY2ZTJjYTQ5ODQiXQ%3D%3D>)