# Maven Central Maven Central is a public repository for open-source Java components and libraries, allowing developers to share and consume Java artifacts. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## Versioned Builds Are Back, With Master Builds For Fast Verification DevFeed: [Versioned Builds Are Back, With Master Builds For Fast Verification]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [releases](), [Development](), [Maven](), [Maven Central](), [Framework]() Tags: [enterprise](), [master](), [production](), [speed](), [verification](), [versioning]() ### AI overview Codename One reintroduces versioned cloud builds, allowing developers to pin builds to a specific published release or build against the current development head. The article explains use cases including production stabilization, regression diagnosis, and reproducing older customer environments, while noting that master builds are intended for verification rather than production shipping and that older versions are limited by account level because of support costs. ### Source excerpt Versioned builds return with a Maven-era model: pin a cloud build to a release, or build against master to verify the current development head. ## 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. ## 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. ## 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 -> ## 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. ## 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. ΠŸΠΎΠ»Π½Ρ‹ΠΉ список ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ доступСн ΠΏΠΎ ссылкС. Π£Π·Π½Π°Ρ‚ΡŒ большС ΠΎ Ρ€Π΅Π»ΠΈΠ·Π΅ ## KotlinDL 0.2: Functional API, Π·ΠΎΠΎΠΏΠ°Ρ€ΠΊ ΠΌΠΎΠ΄Π΅Π»Π΅ΠΉ c ResNet ΠΈ MobileNet, DSL для ΠΎΠ±Ρ€Π°Π±ΠΎΡ‚ΠΊΠΈ ΠΈΠ·ΠΎΠ±Ρ€Π°ΠΆΠ΅Π½ΠΈΠΉ DevFeed: [KotlinDL 0.2: Functional API, Π·ΠΎΠΎΠΏΠ°Ρ€ΠΊ ΠΌΠΎΠ΄Π΅Π»Π΅ΠΉ c ResNet ΠΈ MobileNet, DSL для ΠΎΠ±Ρ€Π°Π±ΠΎΡ‚ΠΊΠΈ ΠΈΠ·ΠΎΠ±Ρ€Π°ΠΆΠ΅Π½ΠΈΠΉ]() Original publisher: [Read original article]() Author: zaleslaw (JetBrains) Published: 2021-05-25T08:54:42Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [Kotlin](), [Deep neural networks](), [Maven Central](), [Tensorflow](), [Keras](), [ImageNet]() Tags: [dataset](), [deep-learning](), [image-processing](), [keras](), [kotlin](), [machine-learning](), [maven-central](), [neural-networks](), [tag-00486ebd8d87](), [tag-9d8cf70dc46c](), [tensorflow]() ### AI overview This article presents KotlinDL 0.2, a deep-learning library written in Kotlin with TensorFlow used for low-level computations. The release adds a Functional API for graph-based neural networks, an image-preprocessing DSL, new dataset types, and a model zoo containing ResNet, MobileNet, and VGG models. KotlinDL 0.2 is available on Maven Central. ### Source excerpt ΠŸΡ€Π΅Π΄ΡΡ‚Π°Π²Π»ΡΠ΅ΠΌ Π²Π°ΠΌ Π²Π΅Ρ€ΡΠΈΡŽ 0.2 Π±ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠΈ KotlinDL. Π­Ρ‚ΠΎ Π±ΠΈΠ±Π»ΠΈΠΎΡ‚Π΅ΠΊΠ° Π³Π»ΡƒΠ±ΠΎΠΊΠΎΠ³ΠΎ обучСния, Π³Π΄Π΅ для Π½ΠΈΠ·ΠΊΠΎΡƒΡ€ΠΎΠ²Π½Π΅Π²Ρ‹Ρ… вычислСний ΠΈΡΠΏΠΎΠ»ΡŒΠ·ΡƒΠ΅Ρ‚ΡΡ TensorFlow, Π½ΠΎ с высокоуровнСвым API ΠΈ Π»ΠΎΠ³ΠΈΠΊΠΎΠΉ, написанными Π½Π° Kotlin. KotlinDL 0.2 Ρ‚Π΅ΠΏΠ΅Ρ€ΡŒ доступСн Π½Π° Maven Central (Π΄ΠΎ этого ΠΎΠ½ Π»Π΅ΠΆΠ°Π» Π½Π° bintray, Π½ΠΎ Π·Π°ΠΊΠ°Ρ‚ΠΈΠ»ΠΎΡΡŒ ΡΠΎΠ»Π½Ρ‹ΡˆΠΊΠΎ Π·Π΅ΠΌΠ»ΠΈ опСнсорсной). Появилось ΡΡ‚ΠΎΠ»ΡŒΠΊΠΎ всСго Π½ΠΎΠ²ΠΎΠ³ΠΎ: Π½ΠΎΠ²Ρ‹Π΅ слои, ΡΠΏΠ΅Ρ†ΠΈΠ°Π»ΡŒΠ½Ρ‹ΠΉ DSL для прСпроцСссинга ΠΈΠ·ΠΎΠ±Ρ€Π°ΠΆΠ΅Π½ΠΈΠΉ, Π½ΠΎΠ²Ρ‹Π΅ Ρ‚ΠΈΠΏΡ‹ датасСтов, Π·ΠΎΠΎΠΏΠ°Ρ€ΠΊ ΠΌΠΎΠ΄Π΅Π»Π΅ΠΉ с нСсколькими модСлями ΠΈΠ· сСмСйства ResNet, MobileNet ΠΈ старой Π΄ΠΎΠ±Ρ€ΠΎΠΉ модСлью VGG (рабочая лошадка, Π²ΠΏΡ€ΠΎΡ‡Π΅ΠΌ). Π’ этой ΡΡ‚Π°Ρ‚ΡŒΠ΅ ΠΌΡ‹ коснСмся самых Π³Π»Π°Π²Π½Ρ‹Ρ… ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ Ρ€Π΅Π»ΠΈΠ·Π° 0.2. ΠŸΠΎΠ»Π½Ρ‹ΠΉ список ΠΈΠ·ΠΌΠ΅Π½Π΅Π½ΠΈΠΉ доступСн ΠΏΠΎ ссылкС. Π§ΠΈΡ‚Π°Ρ‚ΡŒ Π΄Π°Π»Π΅Π΅ ## Building Codename One From Source - Maven Edition DevFeed: [Building Codename One From Source - Maven Edition]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2021-04-21T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Maven](), [Tutorial](), [Maven Central]() Tags: [build](), [building](), [contribute](), [how-to](), [install](), [learn](), [local](), [maven-central](), [projects]() ### AI overview A tutorial on building Codename One from source with Maven, installing it in the local Maven repository, and using that local version in Codename One projects. ### Source excerpt Learn how to build Codename One from source and use this "local" version in your Codename One projects. ## Publishing Codename One Libraries on Maven Central DevFeed: [Publishing Codename One Libraries on Maven Central]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2021-04-19T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Maven Central](), [Maven](), [Publishing](), [Java](), [XML](), [App]() Tags: [build](), [dependency](), [deployment](), [developers](), [how-to](), [java](), [libraries](), [maven-central](), [xml]() ### AI overview This tutorial explains how to publish Codename One libraries to Maven Central so app developers can use them through Maven dependency snippets. It describes the previous .cn1lib distribution process, the Maven-based alternative, continued Codename One Settings support, and manual installation for libraries not yet on Maven Central. ### Source excerpt One of the cool things about Maven is Maven Central - the repository that contains every version of every Java library (that has been published on Maven central at least). Once your library is published, it can be used by other projects by copying and pasting an XML snippet into their pom.xml file. In this article, I describe how to publish your Codename One libraries to Maven central so that app developers can use them in their projects. ## Building Kotlin/Multiplatform with Github Actions DevFeed: [Building Kotlin/Multiplatform with Github Actions]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2021-04-15T11:44:49Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [GitHub Actions](), [Kotlin Multiplatform](), [CI/CD](), [kotlin-multiplatform-libraries](), [Maven Central](), [Gradle](), [HTTP](), [API]() Tags: [ci-cd](), [github](), [github-actions](), [gradle](), [http](), [kotlin](), [kotlin-multiplatform](), [kotlin-multiplatform-libraries](), [maven-central]() ### AI overview This tutorial explains how to automate Kotlin Multiplatform library publishing with GitHub Actions. It covers publishing snapshots to Maven Central, building across Linux, macOS, and Windows, and managing a shared Sonatype staging repository for stable releases. ### Source excerpt In a previous tutorial, I showed you how to configure your Kotlin/Multiplatform libraries to be published on Maven Central. To go beyond a publication process we now need to automate things with a good CI/CD workflow. Let's see how to do this with Github Actions. As the Kodein Open Source Initiative libraries are hosted on Github, we felt that it was the best choice to use the Github Actions pipelines to test, build and deploy our libraries, as it is entirely integrated with every other part of Github. Let's start with the snapshot publication process, as it is fairly straightforward. Publishing snapshots on Maven Central has no more constraints than just being authenticated with your Sonatype account, and having your artifacts file names ending with the uppercased word SNAPSHOT. This means that you could literally upload anything in your staging repositories. Here is a Github Actions script to upload a snapshot of a Kotlin/Multiplatform project: https://medium.com/media/41c7ac097f1ff802076f92acc8243077/href In that example, we run the task publishAllPublicationToOss on Linux, Mac & Windows, literally saying to publish every available targets onto the oss repository, which is the name we gave to it in our maven-publish configuration in our Gradle build script. This is not optimal, as every platform could upload shared targets like JVM, JS or even the Kotlin Multiplatform Metadata, but it's simple, and it works! Let's now see how to deploy stable releases. We have to discuss how we will be managing the unique staging repository we need. In fact, this is quite simple, and it is resume by this image: What we need is to create a staging repository, by using the sonatype API over HTTP. This step will generate a repository ID, that we use in later steps. In the build-upload matrix, we upload every artifact onto the same staging repository. Finally, In the drop-or-release job, depending on the success or failure of the build-upload matrix, we drop or release the staging re ## Migrating Your Project to Maven DevFeed: [Migrating Your Project to Maven]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2021-04-14T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Maven](), [migration](), [Java](), [Maven Central]() Tags: [build](), [build-tool](), [java](), [maven-central](), [migration](), [zip]() ### AI overview This tutorial explains how to migrate existing Codename One Ant application and library projects to Maven. It introduces the Codename One Migration tool, describes its Java 8 or later requirement and lack of dependencies beyond Java, and outlines how to download and open it. ### Source excerpt As you may know, we are moving to Maven for our build tool. As part of this transition, we are moving towards a single Maven project structure, and away from separate structures for each IDE. This will be easier to maintain, and will also make it easier to collaborate on projects with other developers who use a different IDE (or no IDE at all). ## Holi: A library of colors, gradients and utils for Jetpack Compose DevFeed: [Holi: A library of colors, gradients and utils for Jetpack Compose]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2021-03-30T07:52:25Z Content type: tutorial Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Compose](), [Android](), [Maven Central](), [Library](), [Open Source]() Tags: [android](), [android-library](), [color-picker-android](), [compose](), [dracula-colors](), [how-to](), [jetpack-compose](), [jetpack-compose-gradients](), [jetpack-compose-library](), [material-color-library-for-android](), [material-colors-for-jetpack-compose](), [maven-central](), [open-source]() ### AI overview Holi is an open-source MIT-licensed library for Jetpack Compose on Android. It provides predefined colors from multiple palettes, gradient-building utilities, and related helper functions, and is available through Maven Central. ### Source excerpt An open-source library of colors, gradients and utils built using Jetpack Compose for Android. Licenced under MIT and available on Maven central. ## Publishing your Kotlin Multiplatform library to Maven Central DevFeed: [Publishing your Kotlin Multiplatform library to Maven Central]() Original publisher: [Read original article]() Author: Ekaterina Petrova Published: 2021-03-25T12:40:40Z Content type: tutorial Language: en Sources: [Kotlin]() Topics: [Kotlin Multiplatform](), [Maven Central](), [Gradle](), [Library](), [Publishing]() Tags: [coding](), [community](), [development](), [engineering](), [gradle](), [inclusive](), [kotlin](), [kotlin-multiplatform](), [library](), [maven-central](), [multiplatform](), [software]() ### AI overview A tutorial on publishing a Kotlin Multiplatform library to Maven Central. It covers Sonatype account registration, group ID ownership verification, GPG key setup, Gradle publication configuration, metadata and Javadocs, and signing artifacts. ### Source excerpt Now when we've built our first Kotlin Multiplatform library and learned about multiplatform library publishing format nothing can stop us from going public and releasing our library to MavenCentral! Registering a Sonatype account If this is your first library, or you've only ever used Bintray to do this before, you will need to first register a Sonatype account. There are many articles describing the registration process on the internet. The one from GetStream is exhaustive and up to date. You can start by following the first four steps, including "Generating a GPG key pair": Register a Jira account with Sonatype (you can use my issue as an example). βœ… Verify your ownership of the group ID you want to use to publish your artifact by creating a GitHub repo. βœ… Generate a GPG key pair for signing your artifacts. βœ… Publish your public key. βœ… Export your private key. βœ… When the Maven repository and signing keys for your library are prepared, we are ready to move forward and set up our build to upload the library artifacts to a staging repository and then release them! Setting up publication Now we need to tell Gradle how to publish our libraries. Most of the work is already done by maven-publish and Kotlin Gradle Plugins - all the required publications are created automatically. We've already seen the result when we published our library to the local Maven repository. But for publishing it to Maven Central we need to take some additional steps: Configure public Maven repository URL and credentials. Provide a description and javadocs for all library components. Sign publications. Let's handle all of these tasks by writing some Gradle scripts! I suggest extracting all the publication-related logic from our library module build.script, so you can easily reuse it for other modules in the future. The most idiomatic and flexible way to do that is to use Gradle's precompiled script plugins. Our build logic will be provided as a precompiled script plugin and could be applied by ## Migrate existing library artifacts from JCenter to Maven Central DevFeed: [Migrate existing library artifacts from JCenter to Maven Central]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2021-03-24T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Maven Central](), [migration](), [Maven](), [Gradle](), [Command-line interface]() Tags: [blogs](), [gradle](), [jcenter](), [maven](), [maven-central](), [mavencentral](), [migrate](), [migration](), [private-key](), [script](), [secrets](), [sonatype]() ### AI overview A tutorial for migrating existing library artifacts from JCenter to Maven Central. It covers enumerating versions, configuring GPG signing, setting up Sonatype credentials, downloading artifacts, adding missing metadata, and signing and uploading each version. ### Source excerpt With JCenter shutting down, many are migrating to Maven Central. And while there are many posts on how to publish new artifacts, also all existing artifacts should be migrated away from JCenter. ## Publish a Kotlin/Multiplatform library on Maven Central DevFeed: [Publish a Kotlin/Multiplatform library on Maven Central]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2021-03-09T15:02:47Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [Kotlin Multiplatform](), [Maven Central](), [Tutorial](), [Gradle](), [Library]() Tags: [dependencies](), [gradle](), [how-to](), [kotlin](), [kotlin-multiplatform](), [maven-central](), [maven-plugin](), [releases](), [sonatype](), [tutorial]() ### AI overview This tutorial explains how to publish a Kotlin Multiplatform library to Maven Central. It covers migrating from Bintray and JCenter, Maven Central's requirements for sources, documentation, POM files, and signatures, and the staging-repository complications that arise in multiplatform builds. ### Source excerpt https://medium.com/media/1f069bfe70a66ec0f8528588ae5ee209/href In our last tutorial, Salomon showed you how to create a Kotlin Multiplatform Mobile library. Now that we have some code ready to be used by the community, let me show you how to publish your future releases to Maven Central. Before going into details about how to deploy your libs to Maven Central, I want to adress library developers who already have a library published on JCenter. This tutorial is also for you! Publishing on Bintray and JCenter was a choice most of us made, because it had less constraints and more flexibility. Now that they will be shutting down quite soon, we must migrate our publication workflow. Maven Central seems to be the right choice these days, but we need to deal with new requirements. Where Bintray was giving us some latitude on what we could upload and publish, Maven Central has always been more restrictive. Indeed, every uploaded artifact needs to be accompanied at least by the following items: A bundle of the sources of the artifact The documentation that goes with the artifact, in the JVM world this is the Javadoc. A well formatted POM file. For those who are not familiar with Maven, this is the description of your project, with its name, its version, its dependencies, etc, in an XML format And finally, every item needs to be signed to be accepted. Actually, these requirements are not that hard to fulfill, and Gradle provides almost everything we need to publish our artifacts smoothly, with 2 official plugins, maven-publish and signing. But... I told you : almost! When performing a publication, before being available on Maven Central, all your uploaded artifacts with maven-publish are generally stored and referenced in one staging repository that you need to validate as the final step of publishing. While this is true for standard JVM projects, this is not the case for Kotlin/Multiplatform ones. As Kotlin/Multiplatform developers, you may know that you need two machines to b ## Migrating away from JCenter DevFeed: [Migrating away from JCenter]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2021-02-04T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Gradle](), [Maven](), [Maven Central](), [Jfrog]() Tags: [android](), [bintray](), [blogs](), [dependencies](), [gradle](), [guide](), [how-to](), [jcenter](), [jfrog](), [library](), [maven](), [maven-central](), [migrate](), [repository](), [transitive-dependencies]() ### AI overview A practical guide to migrating Gradle dependencies and published artifacts away from Bintray/JCenter after JFrog announced the repository shutdown. It explains replacing JCenter with Maven Central, testing clean builds, and restricting remaining dependencies to explicit repository declarations. ### Source excerpt This week JFrog - out of nowhere - announced to completely remove their Maven repository. Since they'll pull it offline already by May 2021 (!!!) it's time to urgently migrate away. ## Android library development - Getting started DevFeed: [Android library development - Getting started]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2020-10-28T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android Library](), [SDK](), [Gradle](), [Library](), [Maven Central](), [LineageOS]() Tags: [android](), [android-library](), [blogs](), [development](), [getting-started](), [gradle](), [kotlin](), [library](), [maven](), [maven-central](), [maven-repository]() ### AI overview This tutorial introduces Android library development and explains how it differs from app development. It covers a typical SDK project structure, building an Android Archive with Gradle, publishing libraries as Maven dependencies, and the implications of external dependencies. ### Source excerpt Having switched to Android SDK development over the past year, I've run into quite a few interesting and unexpected challenges. So how does library development differ from app development? [Next page]()