# Maven Central Published articles for Maven Central. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs DevFeed: [WorkOS announces Agent Registration, Airlock, Relay, and native iOS and Android SDKs]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [WorkOS Blog]() Topics: [SDKs](), [Android](), [iOS](), [Authorization](), [Mobile](), [Claude](), [Kotlin](), [Swift](), [MCP](), [Coroutines](), [Claude Code](), [codex]() Tags: [agent](), [android](), [api](), [authorization](), [await](), [claude](), [claude-code](), [coroutines](), [ios](), [kotlin](), [maven-central](), [mcp](), [sdks](), [swift](), [updates]() ### AI overview WorkOS announces August updates including Agent Registration for scoped, short-lived credentials, Airlock for authorizing AI-agent actions, Relay for proxying third-party application requests, and native Swift and Kotlin SDKs for iOS and Android. ### Source excerpt Agent Registration, Airlock, Relay, iOS & Android SDKs, & more ## Add sign-in to an Android app with the WorkOS Android SDK DevFeed: [Add sign-in to an Android app with the WorkOS Android SDK]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-24T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [Android](), [SDKs](), [Kotlin](), [Authentication](), [pkce](), [Gradle](), [Coroutines](), [API keys](), [Security](), [Maven Central](), [Mobile]() Tags: [android](), [api](), [api-keys](), [authentication](), [coroutines](), [flow](), [gradle](), [kotlin](), [maven-central](), [pkce](), [sdk](), [security](), [sign-in](), [tutorial]() ### AI overview This tutorial shows how to add WorkOS AuthKit sign-in to a Kotlin Android app using the WorkOS Android SDK. It covers the Gradle dependency, Chrome Custom Tab authentication, custom-scheme redirects, PKCE token exchange, session storage and refresh, and logout without embedding a client secret in the APK. ### Source excerpt Build a complete AuthKit flow in Kotlin, from Gradle dependency to signed-out state, with no client secret in your APK. ## Why Codename One Is Moving Beyond Maven Central DevFeed: [Why Codename One Is Moving Beyond Maven Central]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-04T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Maven Central](), [migration](), [Cloudflare](), [Maven](), [hosting](), [Open Source](), [releases]() Tags: [cloudflare](), [hosting](), [maven-central](), [migration](), [open-source](), [releases]() ### AI overview Codename One is moving from Maven Central to a repository operated on Cloudflare R2. The staged migration includes a smaller release payload, dual publishing during the transition, and a planned cutover; the August 28, 2026 update says new releases now go only to the Codename One repository. ### Source excerpt Codename One is starting a staged move from Maven Central to a free Cloudflare R2 repository, with dual publishing, a smaller release payload, and an explicit cutover plan. ## Hardwood 1.0: A Fast, Lightweight Apache Parquet Reader for the JVM DevFeed: [Hardwood 1.0: A Fast, Lightweight Apache Parquet Reader for the JVM]() Original publisher: [Read original article]() Published: 2026-06-25T05:30:00Z Content type: release Language: en Sources: [Gunnar Morling]() Topics: [parquet](), [releases](), [Java](), [Library](), [Open Source](), [Maven Central]() Tags: [apache-parquet](), [compatibility](), [compression](), [cpu](), [java](), [jvm](), [library](), [maven-central](), [open-source](), [parquet](), [performance](), [releases]() ### AI overview The article announces Hardwood 1.0, an open-source Apache Parquet library for Java 21 or newer and the JVM. It focuses on fast, multi-threaded reading with no mandatory dependencies, supports local and remote files, and is available from Maven Central. ### Source excerpt Table of Contents Why Hardwood What's in Hardwood 1.0 Performance The Hardwood CLI Building Open-Source With AI A Big Thank You What's Ahead Hardwood is a new Parquet library for the JVM, written from scratch to do one thing well: read (and soon, write) Apache Parquet files fast, with no mandatory dependencies. It is performance-focused and multi-threaded at its core, fanning page decoding out across all your CPU cores by default. Today, Hardwood reaches 1.0. After five preview releases since the start of the year (Alpha1, Beta1, Beta2, CR1, CR2), we now consider Hardwood ready for production, and its public API will evolve with a strong focus on backwards compatibility going forward. Hardwood targets Java 21 or newer, is open-source (Apache License 2.0), and is available from Maven Central. ## Apollo Kotlin 5 Is Now Available DevFeed: [Apollo Kotlin 5 Is Now Available]() Original publisher: [Read original article]() Author: Martin Bonnin Published: 2026-05-13T12:00:25Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Kotlin](), [GraphQL](), [Cache](), [Caching](), [Gradle](), [Maven Central](), [Agent Skills]() Tags: [agent-skills](), [cache](), [changelog](), [community](), [gradle](), [gradle-plugin](), [graphql](), [kotlin](), [kotlin-multiplatform](), [maven-central]() ### AI overview Apollo Kotlin 5 is available on Maven Central with GraphQL Golden Path support, a new normalized cache, a modernized Gradle plugin, compiler plugin APIs, and an Apollo Kotlin agent skill. The release includes experimental GraphQL RFC support and provides a migration path from version 4. ### Source excerpt Apollo Kotlin 5 is now available on Maven Central. GraphQL Golden Path ready, with a new normalized cache, agent skills support, and a modernized Gradle plugin. ## Your riskiest supplier isn't a vendor. It's a registry. DevFeed: [Your riskiest supplier isn't a vendor. It's a registry.]() Original publisher: [Read original article]() Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [Security](), [Open Source](), [npm](), [Maven](), [pip]() Tags: [apra](), [apra-compliance](), [auditability](), [chainguard-libraries](), [cps-230](), [cps-234](), [maven-central](), [npm](), [pypi](), [resilience](), [security](), [supply-chain]() ### AI overview The article argues that public package registries such as npm, PyPI, and Maven Central create an assurance gap for APRA-regulated institutions because organizations may consume artifacts without independently verifying their source or build process. It recommends source-built libraries as a more defensible approach to managing malware risk, operational resilience, and auditability. ### Source excerpt Public registries create supply chain risk. Learn how source-built libraries help APRA-regulated teams improve security, resilience, and auditability. ## Hardwood: A New Parser for Apache Parquet DevFeed: [Hardwood: A New Parser for Apache Parquet]() Original publisher: [Read original article]() Published: 2026-02-26T12:30:00Z Content type: release Language: en Sources: [Gunnar Morling]() Topics: [parquet](), [Parser](), [Java](), [Open Source](), [Compression](), [DuckDB]() Tags: [apache-parquet](), [compression](), [dependencies](), [java](), [maven-central](), [open-source](), [parquet](), [parsing](), [performance](), [release]() ### AI overview The article announces Hardwood, an open-source Java 21+ parser for Apache Parquet. It is designed to minimize dependencies and improve parsing performance through a multithreaded decoding pipeline, with optional libraries for Parquet compression algorithms. The article also introduces Maven setup and row-oriented and columnar APIs. ### Source excerpt Table of Contents Why Hardwood? Hello, Hardwood! Parsing Performance Built With AI, Not By AI What's Next? Today, it's my great pleasure to announce the first public release of Hardwood, a new parser for the Apache Parquet file format, optimized for minimal dependencies and great performance. Hardwood is open-source (Apache License 2.0) and supports Java 21 or newer. You can grab it from Maven Central and start parsing your Parquet files with ease and efficiency. ## Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas DevFeed: [Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas]() Original publisher: [Read original article]() Author: Steve Poole Published: 2025-12-24T03:03:09Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [Python](), [pip](), [PyPI](), [Maven Central](), [Java](), [Maven]() Tags: [2025](), [attacks](), [dependency](), [developer](), [guide](), [install](), [internet](), [java](), [maven-central](), [mirror](), [model](), [packaging](), [pitfalls](), [pypi](), [python](), [registry](), [trust]() ### AI overview A Java-focused guide to Python package-management risks. It contrasts Maven Central with PyPI, highlighting flat package naming, trusting dependency resolution, typosquatting, dependency confusion, and unsafe installation commands. It recommends version pins, known sources, private registries, and lock files. ### Source excerpt Just like that it happened. You, a disciplined Java developer, are now installing Python. Like everything in 2025, it just arrived. One day, you were running a tidy mvn install, the next, you're learning about virtual environments and fighting an unfriendly pip install that won't explain what it just pulled from the internet. Good news: [...] The post Santa's Python Pitfalls: A Java Developer's Guide to Staying Safe This Christmas appeared first on JVM Advent. ## Good Neighbors: How to Reduce Maven Central Traffic from Gradle Builds DevFeed: [Good Neighbors: How to Reduce Maven Central Traffic from Gradle Builds]() Original publisher: [Read original article]() Author: Louis Jacomet Published: 2025-08-01T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Caching](), [Programming](), [Java](), [Kotlin](), [CI/CD](), [Automation]() Tags: [automation](), [caching](), [ci-cd](), [gradle](), [how-to](), [java](), [jvm](), [maven-central]() ### AI overview This article explains how organizations can reduce Maven Central traffic from Gradle builds by using an internal caching Maven repository proxy. It discusses the cost, delay, slowdown, and throttling risks of direct access, and describes configuring Gradle's centralized repository declarations to route dependency resolution through the organization's repository. The configuration also affects plugin dependency resolution through the Gradle Plugin Portal. ### Source excerpt Maven Central is a vital resource for Java, Kotlin, and other JVM communities. It provides the most popular repository for open source libraries, developer tools, documentation, and other artifacts. This service is heavily used not only by developers but also by CI/CD pipelines and automation tools. While it's best practice to use a caching proxy for Maven Central, not everyone does. This results not only in excessive traffic costs and build delays but also exposes your builds and pipelines to more slowdowns and failures due to throttling mechanisms to protect Maven Central. As Brian Fox, Sonatype's CTO, wrote in this blog post in June 2024, "83% of the total bandwidth of Maven Central is being consumed by just 1% of the IP addresses. Further, many of those IPs originate from some of the world's largest companies... we will start to work with our providers to implement throttling mechanisms aimed at the extremely heavy consumers, which are effectively abusing a community resource." As this work progresses, more organizations will face throttling, including those using Gradle, especially if they rely heavily on Maven Central without a caching proxy in place. While Gradle currently does not have a built-in equivalent of Maven's mirrorOf feature to route all dependency resolution through a caching proxy, organizations can deploy a configuration that has the same effect and is compatible with existing Gradle releases. This is possible thanks to Gradle's flexibility and rich programming model. ℹ What about the Gradle Plugin Portal? In this blog post, we showcase configuration changes that also impact the use of the Gradle Plugin Portal for resolving plugin dependencies. This is also a community resource provided for free by Gradle Inc. and, just like Maven Central, it needs to manage its workload and bandwidth usage. Note that the Plugin Portal also uses rate limiting for artifact resolution to cope with the increasing load. Using an internal artifact repository Having a ## How Chainguard Libraries for Java Secures Dependencies at Maven Central Scale DevFeed: [How Chainguard Libraries for Java Secures Dependencies at Maven Central Scale]() Original publisher: [Read original article]() Published: 2025-06-25T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard libraries](), [Java](), [Reverse Dependencies](), [Maven](), [Open Source]() Tags: [central](), [chainguard-libraries](), [chainguard-libraries-for-java](), [dependencies](), [graph](), [java](), [java-libraries](), [java-packages](), [libraries](), [maven-central](), [open-source](), [supply-chain]() ### AI overview This article explains how Chainguard is building Chainguard Libraries for Java to secure open-source JVM dependencies from Maven Central. It describes the repository's scale and the initial selection strategy, which uses dependency-graph data to identify popular libraries and prioritizes newer projects. ### Source excerpt Chainguard Libraries for Java is Chainguard's repository of malware-resistant Java dependencies. Learn how we are building and maintaining over 50,000 projects. ## New Maven Central signing key and snapshot location DevFeed: [New Maven Central signing key and snapshot location]() Original publisher: [Read original article]() Author: Jake Wharton Published: 2025-06-13T00:00:00Z Content type: release Language: en Sources: [Cash App Code Blog]() Topics: [Maven Central](), [Maven](), [Publishing](), [Open Source]() Tags: [end-of-life](), [maven-central](), [open-source-artifacts](), [public-key](), [release](), [server-android](), [signing](), [snapshot](), [snapshots](), [verification]() ### AI overview Cash App migrated its open source artifact publishing to Sonatype's new platform after OSSRH reached end of life. The change introduces a company-wide GPG signing key and moves snapshot builds to the Central Portal Snapshot repository. ### Source excerpt In response to Sonatype announcing the end-of-life for OSSRH, we have migrated to their new publishing platform for our open source artifacts. This is otherwise a transparent change for those who consume these artifacts from Maven Central, but there are two related changes which might affect your builds. ## Impact of final JCenter shutdown on Gradle Plugin Portal DevFeed: [Impact of final JCenter shutdown on Gradle Plugin Portal]() Original publisher: [Read original article]() Author: Louis Jacomet Published: 2024-07-05T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Package manager](), [configuration]() Tags: [analysis](), [blog-post](), [build](), [dependencies](), [gradle](), [jfrog](), [maven-central](), [proxy]() ### AI overview The article analyzes the impact of JCenter becoming a permanent redirect to Maven Central on the Gradle Plugin Portal and Gradle builds. It explains the portal's move from acting as a JCenter proxy to a Maven Central proxy and identifies plugin and transitive-dependency resolution failures that users may encounter. ### Source excerpt ℹ Update on July 15, 2024 We have found errors causing false positive in failed plugin resolution. 4 plugins have been removed from the list, resulting in 9 removed dependencies. We also added 105 plugins that depend on one or more affected plugins. These will fail to resolve transitively. Not taking exclude into account caused the first change, the second one came from not taking plugin dependencies into account. Now that JFrog has confirmed that JCenter will become a permanent redirect to Maven Central, we felt that it was important for the Gradle Plugin Portal users to understand the impact of that decision on the portal and their builds. This post follows our report after JCenter redirected to Maven Central for a day. Users still directly using JCenter should also refer to our original blog post about the changes in JCenter and their impact on Gradle builds in general. Upcoming Plugin Portal changes JCenter will become a permanent redirect to Maven Central. As a consequence, the Gradle Plugin Portal will no longer act as a JCenter proxy and will instead become a Maven Central proxy. The Gradle Plugin Portal will continue to return redirects (303 See Other) for artifact queries it cannot serve. Starting July 15, 2024, these redirects will be towards Maven Central instead of JCenter. This change might impact existing Gradle builds: Build using plugins with dependencies that are exclusively available on JCenter will fail to resolve. Builds configured to use the Gradle Plugin Portal as a regular artifact repository (which is not recommended) may be impacted. For more information, refer to our original blog post. We aim to document the potential impact on Gradle plugins provided by the Plugin Portal. Read our analysis below to learn how to minimize the impact on your builds. Impact analysis We have performed two major analyses: For all the plugins known to the Gradle Plugin Portal, determine which ones would fail to resolve if their transitive dependencies are resol ## Lessons Learned Releasing the Markdown Twain Jetpack Compose Library DevFeed: [Lessons Learned Releasing the Markdown Twain Jetpack Compose Library]() Original publisher: [Read original article]() Published: 2024-04-22T15:47:29Z Content type: opinion Language: en Sources: [Colin The Shots]() Topics: [Compose](), [Jetpack Compose](), [Library](), [Kotlin](), [Kotlin Multiplatform](), [Open Source](), [Gradle](), [Maven Central]() Tags: [android](), [compose](), [gradle](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [libraries](), [maven-central](), [open-source]() ### AI overview A software developer recounts releasing Markdown Twain, a WYSIWYG Markdown editor for Jetpack Compose, as open source. The article explains how rushed packaging and configuration, including Maven publishing and testing against source code instead of Maven Central, obscured errors and provides lessons from the release. ### Source excerpt Introduction As a seasoned software developer deeply immersed in the world of Android, Kotlin, and Jetpack Compose, I've always been driven by a passion for creating tools that empower developers. My ## Maven Coordinates of the most popular JDBC Drivers DevFeed: [Maven Coordinates of the most popular JDBC Drivers]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-13T11:25:44Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Maven](), [Maven Central](), [Database]() Tags: [database](), [drivers](), [integration](), [java](), [jdbc](), [jdbc-drivers](), [jooq](), [maven](), [maven-central](), [sql]() ### AI overview A list of Maven coordinates for popular JDBC drivers used in jOOQ integration tests, with guidance to verify current versions on Maven Central and check driver licenses before downloading. ### Source excerpt Do you need to add a JDBC driver to your application, and don't know its Maven coordinates? This blog post lists the most popular drivers from the jOOQ integration tests. Look up the latest versions directly on https://central.sonatype.com/ with parameters g:groupId a:artifactId, for example, the H2 database and driver: https://central.sonatype.com/search?q=g%3Acom.h2database+a%3Ah2 The list only includes drivers ... Continue reading Maven Coordinates of the most popular JDBC Drivers -> ## Plugin Portal Outage Followup DevFeed: [Plugin Portal Outage Followup]() Original publisher: [Read original article]() Author: Sterling Greene Published: 2023-06-28T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Library]() Tags: [bintray](), [blog-post](), [dependencies](), [gradle](), [gradle-plugin](), [jfrog](), [libraries](), [maven-central](), [outage](), [plugin]() ### AI overview This follow-up explains how an unannounced JCenter change on June 23, 2023 caused Gradle users to experience failures resolving artifacts through the Gradle Plugin Portal. It describes the impact on plugin builds, missing artifacts and transitive dependencies, recovery options, and plans to reduce reliance on JCenter. ### Source excerpt ℹ Update on July 15, 2024 See our recent blog post for up-to-date information about the Plugin Portal and JCenter. On June 23rd, 2023, at 9:00 UTC, Gradle users started experiencing issues resolving artifacts from the Gradle Plugin Portal because of changes to artifacts hosted on JCenter by JFrog. JCenter stopped serving files directly and redirected all requests to Maven Central. This was an unannounced change. We contacted JFrog, and they replied it was a test and they would revert back to having JCenter serve artifacts. Around 18:30 UTC, JCenter returned to normal behavior. This post describes the effect this outage had on builds, ways to recover from similar outages, and what we will do to eliminate the dependency on JCenter in the future. Users still directly using JCenter should also refer to our original blog post about the shutdown of JCenter on Gradle builds in general. Effects on Gradle plugins usage in builds When JFrog stopped serving artifacts from JCenter, all requests were redirected to Maven Central. This can impact builds in different ways. In this blog post, we focus on the resolution of Gradle plugins from the Plugin Portal. Background information The Plugin Portal only hosts artifacts related to Gradle plugins. The Plugin Portal redirects Gradle builds to JCenter to resolve transitive dependencies required by plugins. Some of these transitive dependencies are hosted by JCenter and some are mirrored from Maven Central. Additionally, some very old versions of Gradle plugins are also hosted on JCenter. This is because they were historically hosted on JFrog's Bintray service. Following Bintray's shutdown in May 2021, we removed the Plugin Portal's integration with Bintray, but we kept redirecting to JCenter for those artifacts because JFrog committed to keeping JCenter read-only indefinitely. When changes are made to JCenter, the Plugin Portal may no longer serve some artifacts or serve different artifacts. Missing artifacts Any artifacts only avail ## Mastering The Gradle Dependency Tree DevFeed: [Mastering The Gradle Dependency Tree]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2023-01-11T23:09:51Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Gradle](), [modules](), [Library](), [Maven Central]() Tags: [debug](), [dependencies](), [dependency](), [gradle](), [library](), [maven-central](), [modularization](), [modules](), [resolved](), [transitive-dependencies]() ### AI overview This tutorial explains Gradle dependencies, transitive dependencies, dependency configurations, and dependency trees. It also presents five ways to generate a dependency tree and discusses managing versions to avoid conflicts and unnecessary project bloat. ### Source excerpt Learn everything about the Gradle Dependency Tree and Five Different Ways to Generate Them. ## The Evolution of Kotlin Multiplatform Mobile - 2022 Edition - Russell Wolf DevFeed: [The Evolution of Kotlin Multiplatform Mobile - 2022 Edition - Russell Wolf]() Original publisher: [Read original article]() Published: 2022-10-31T18:13:15Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [kotlin multiplatform mobile](), [multiplatform](), [Kotlin](), [Mobile](), [kotlin-native](), [Gradle](), [cocoapods](), [Library](), [swift-package-manager](), [swift-package](), [Maven Central]() Tags: [cocoapods](), [gradle](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [kotlin-native](), [libraries](), [maven-central](), [mobile](), [multiplatform]() ### AI overview This retrospective traces Kotlin Multiplatform Mobile from its early experimental stage, when Kotlin/Native memory management, Gradle configuration, and Xcode integration were difficult, to a more mature state with improved memory management, iOS integration through CocoaPods and Swift Package Manager, and better Kotlin-to-Swift interoperability. It also describes growth in the KMM library ecosystem, from about five published libraries in 2018 to more than 1,000 relevant artifacts on Maven Central. ### Source excerpt Kotlin Multiplatform has come a long way in the last few years. As someone who was there when the KMP community first formed, I've seen the ecosystem grow from a few developers trying things out experimentally to a growing number of teams using it in their production apps. With the Kotlin Multiplatform Mobile Beta freshly announced, it's a neat moment to look back on how far everything has come. How It Started In the early days, KMP wasn't very easy for new users. ## Automate library publishing to Maven Central with GitHub Actions Workflow Dispatch 🤖 DevFeed: [Automate library publishing to Maven Central with GitHub Actions Workflow Dispatch 🤖]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2022-01-21T12:49:26Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [GitHub Actions](), [Maven Central](), [Library](), [releases](), [ci](), [Maven]() Tags: [android](), [ci](), [github](), [github-actions](), [gradle](), [guide](), [java](), [kotlin](), [libraries](), [library](), [maven](), [maven-central](), [releases](), [source](), [workflow]() ### AI overview A step-by-step guide to using GitHub Actions Workflow Dispatch to manually build a JVM library, publish it to Maven Central, create a version tag, and create a draft release. ### Source excerpt Step-by-step guide to automating JVM library publishing to Maven Central using GitHub Actions and Workflow Dispatch for one-click releases. ## Gradle Plugin Resolution Outage Postmortem DevFeed: [Gradle Plugin Resolution Outage Postmortem]() Original publisher: [Read original article]() Author: Louis Jacomet Published: 2022-01-20T05:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [incident](), [Maven]() Tags: [build](), [dependencies](), [gradle](), [incident](), [maven-central](), [mirror](), [outage](), [plugin]() ### AI overview This postmortem examines the January 12, 2022 outage that disrupted Gradle Plugin Portal plugin resolution because of its dependency on JCenter. It presents the incident timeline, the effects on builds, the fixes deployed, and measures to reduce reliance on JCenter, including repository content filtering, metadata sources, an internal mirror, and Maven Central. ### Source excerpt On January 12th 2022, Gradle users were experiencing issues resolving plugins from the Gradle Plugin Portal because of the outage of JCenter that the Plugin Portal depends on for some of the functionality. This postmortem gives a timeline of the outage, describes the effect on Gradle users, and what actions were taken to further reduce the Gradle Plugin Portal's reliance on JCenter. Finally, we will also discuss how you can protect your build against such outages. Users affected by JCenter outages for project dependencies should also refer to our original blog post about the shutdown of JCenter. Outage timeline 4.30pm UTC, January 12th Outage begins Gradle users start noticing that plugin resolution is failing in builds. 4.56pm UTC, January 12th Incident opened The outage is acknowledged on the Gradle status page. 6pm UTC, January 12th We identify a hotfix that will allow the Gradle Plugin Portal to ignore 5xx error codes from JCenter and resolve plugins it hosts entirely. However, the hotfix cannot be built and deployed immediately because building the Plugin Portal code requires resolving some plugins from the Plugin Portal itself and JCenter, which failed. 8.44pm UTC, January 12th First fix is deployed We update the build of the Plugin Portal to not rely on JCenter at all by using repository content filtering and supported metadata sources. The first fix is deployed. 8.58pm UTC, January 12th Second fix is deployed The first fix turns out to be insufficient. We develop and deploy a second fix that allows us to change the repository to which the Plugin Portal redirects. We configure the Plugin Portal to use our internal mirror of JCenter. 9.43pm UTC, January 12th Outage is resolved The existing mirror is too sparsely populated as it was not used much, which means most builds still fail to resolve plugins. We update the mirror repository to redirect to Maven Central as well. This results in most dependencies being properly resolved and unblocked most builds. Plugins ## openHAB 3.2 Release DevFeed: [openHAB 3.2 Release]() Original publisher: [Read original article]() Published: 2021-12-20T20:00:00Z Content type: release Language: en Sources: [openHAB]() Topics: [releases](), [log4j](), [Open Source](), [Maintainers](), [Maven Central]() Tags: [log4j](), [maintainers](), [maven-central](), [open-source](), [release](), [releases]() ### AI overview The openHAB 3.2 winter release adds new add-ons, enhanced voice features, and automation improvements. It includes log4j 2.17 after earlier openHAB patch releases addressed Log4Shell risks, and the announcement recognizes open-source maintainers and contributors. ### Source excerpt Having said this, I would like to also make sure that our openHAB committers are recognized for their work. While I often do the announcements, I don't contribute to the code base that much anymore - the major work is on the shoulders of many individuals that - most of the time silently - keep coding and contributing to our common project. I therefore like to thank every contributor, especially the ones of the 18 new add-ons that are included in the 3.2 release and would now like to give the word directly to some of our maintainers that worked on outstanding new features: ## Introducing Apollo Kotlin DevFeed: [Introducing Apollo Kotlin]() Original publisher: [Read original article]() Author: Martin Bonnin Published: 2021-12-16T15:15:14Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [Kotlin](), [GraphQL](), [client](), [multiplatform](), [Caching](), [Android](), [iOS]() Tags: [2](), [2-0-0](), [android](), [announcement](), [apollo](), [build](), [caching](), [concurrency](), [coroutines](), [feature](), [graphql](), [improvements](), [ios](), [js](), [kotlin](), [linux](), [macos](), [maven-central](), [multiplatform](), [new-features](), [sqldelight]() ### AI overview Apollo announces Apollo Kotlin, the renamed and fully Kotlin-based successor to Apollo Android. Apollo Kotlin is a type-safe, caching GraphQL client that generates models from GraphQL queries and adds multiplatform support, coroutine APIs, response-based code generation, SQLite batching, test builders, and cache policy directives. ### Source excerpt We're thrilled to announce Apollo Kotlin! For the past while we've been heads down converting Apollo Android to be 100% Kotlin based, which means Apollo Android now works with any Kotlin based application, website or even server. Because of this, we're renaming the project to Apollo Kotlin! Apollo Kotlin is a type-safe, caching GraphQL client. ## The Evolution of Kotlin Multiplatform Mobile - 2022 Edition (OLD) - Russell Wolf DevFeed: [The Evolution of Kotlin Multiplatform Mobile - 2022 Edition (OLD) - Russell Wolf]() Original publisher: [Read original article]() Published: 2021-11-01T15:31:26Z Content type: opinion Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Kotlin Multiplatform](), [kotlin multiplatform mobile](), [Kotlin](), [multiplatform](), [Library](), [Maven Central](), [jetbrains]() Tags: [evolution](), [jetbrains](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-mobile](), [kotlin-native](), [libraries](), [maven-central](), [mobile](), [multiplatform]() ### AI overview Russell Wolf reviews the evolution of Kotlin Multiplatform Mobile from its early experimental period to broader production use. The article describes improvements in Kotlin/Native memory management, Xcode integration, dependency distribution, Swift interoperability, and the growth of the KMM library ecosystem. ### Source excerpt Touchlab's Russell Wolf looks at how the evolution of KMM has been playing out since the first introduction of Kotlin Multiplatform to today ## KotlinDL 0.3: поддержка ONNX, Object Detection API, 20+ новых моделей в ModelHub, и много новых слоев DevFeed: [KotlinDL 0.3: поддержка ONNX, Object Detection API, 20+ новых моделей в ModelHub, и много новых слоев]() Original publisher: [Read original article]() Author: zaleslaw (JetBrains) Published: 2021-10-04T13:56:53Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [onnx](), [object-detection](), [Maven](), [Maven Central](), [Artificial Intelligence](), [Keras](), [PyTorch]() Tags: [big-data](), [central](), [deep-learning](), [fine-tuning](), [image-recognition](), [keras](), [kotlin](), [machine-learning](), [maven-central](), [object-detection](), [onnx](), [onnx-runtime](), [pytorch](), [tensorflow]() ### AI overview This release article presents KotlinDL 0.3, adding ONNX model support through ONNX Runtime Java API, new ModelHub models, an experimental high-level image-recognition API, additional layers, and Maven Central availability. It also describes object-detection support and fine-tuning limitations for ONNX models. ### Source excerpt Представляем версию 0.3 библиотеки глубокого обучения KotlinDL! Вас ждет множество новых фич: новые модели в ModelHub (включая модели для обнаружения объектов и распознавания лиц), возможность дообучать модели распознавания изображений, экспортированные из Keras и PyTorch в ONNX, экспериментальный высокоуровневый API для распознавания изображений и множество новых слоев, добавленных контрибьюторами. Также KotlinDL теперь доступен в Maven Central. В этой статье мы коснемся самых главных изменений релиза 0.3. Полный список изменений доступен по ссылке. Узнать больше о релизе ## Introducing JfrUnit 1.0.0.Alpha1 DevFeed: [Introducing JfrUnit 1.0.0.Alpha1]() Original publisher: [Read original article]() Published: 2021-08-04T17:10:00Z Content type: release Language: en Sources: [Gunnar Morling]() Topics: [JDK Flight Recorder](), [Unit testing](), [Testing](), [Java](), [Quarkus](), [Groovy](), [Maven]() Tags: [groovy](), [java](), [jdk-flight-recorder](), [junit](), [jvm](), [maven-central](), [quarkus](), [testing](), [unit-testing]() ### AI overview The article announces JfrUnit 1.0.0.Alpha1, a JUnit extension for asserting JDK Flight Recorder events in unit tests. It describes uses including validating custom events, detecting potential performance regressions, and white-box testing with JMC Agent, and outlines setup and usage with Maven, Quarkus, Groovy, and Spock examples. ### Source excerpt Table of Contents Getting Started With JfrUnit Groovier Tests With Spock Outlook Unit testing, for performance It's with great pleasure that I'm announcing the first official release of JfrUnit today! JfrUnit is an extension to JUnit which allows you to assert JDK Flight Recorder events in your unit tests. This capability opens up a number of interesting use cases in the field of testing JVM-based applications: You can use JfrUnit to ensure your application produces the custom JFR events you expect it to emit You can use JfrUnit to identify potential performance regressions of your application by means of tracking JFR events e.g. for garbage collection, memory allocation and network I/O You can use JfrUnit together with JMC Agent for whitebox tests of your application, ensuring specific methods are invoked with the expected parameters and return values [Next page]()