# Maven Published articles for Maven. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## IntelliJ IDEA 2026.2.3 Is Out! DevFeed: [IntelliJ IDEA 2026.2.3 Is Out!]() Original publisher: [Read original article]() Author: Maria Kosukhina Published: 2026-09-16T10:53:53Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [2026.2](), [Release notes](), [releases](), [Maven](), [Markdown](), [plantuml](), [WSL2](), [Ubuntu]() Tags: [2026-2](), [intellij-idea](), [markdown](), [maven](), [plantuml](), [release-notes](), [ubuntu](), [wsl2]() ### AI overview JetBrains released IntelliJ IDEA 2026.2.3 with fixes and improvements affecting Maven project data, IDE freezes, Markdown preview scrolling, PlantUML support, and applications using WSL2 mirrored networking. ### Source excerpt We've just released IntelliJ IDEA 2026.2.3. You can update to this version from inside the IDE, using the Toolbox App, or using snaps if you are a Ubuntu user. You can also download it from our website. The latest update brings the following improvements: For a comprehensive overview of the fixes, see the release notes. [...] ## AppFunctions, revisited DevFeed: [AppFunctions, revisited]() Original publisher: [Read original article]() Author: Thomas Künneth Published: 2026-07-25T11:36:27Z Content type: tutorial Language: en Sources: [Thomas Künneth]() Topics: [Jetpack](), [Android](), [Library](), [implementation](), [Maven]() Tags: [ai](), [android](), [androiddev](), [article](), [code](), [coding](), [community](), [development](), [engineering](), [implementation](), [inclusive](), [jetpack](), [library](), [maven](), [programming](), [software](), [update]() ### AI overview This tutorial revisits Android Jetpack AppFunctions after alpha10 stopped publishing appfunctions-service. It explains the new service entry-point model, generated subclasses and XML, manual service declaration, the removal of AppFunctionContext, and a correction about using installed-app display names instead of package names. ### Source excerpt In Agentic interaction using AppFunctions I showed how Be nice publishes createAppPair for agents, using Jetpack appfunctions 1.0.0-alpha08. That setup leaned on a library-merged PlatformAppFunctionService, an AppFunctionContext parameter, and aggregate XML named app_functions.xml / app_functions_v2.xml. When I bumped toward what Android Studio was suggesting as of mid July, Sync failed: Could not find androidx.appfunctions:appfunctions-service:1.0.0-alpha10. On 1 July 2026, alpha10 stopped publishing appfunctions-service (Maven still lists it through alpha09). The Add the AppFunctions API guide now expects you to host an @AppFunctionServiceEntryPoint AppFunctionService. Spoiler: that is the real change. The rest of this post is how that landed in Be nice, plus an important update to the earlier article that is easy to miss if you only chase compile errors. Correction first In the earlier post I wrote that agents would pass package names for app1 and app2. That was wrong for Be nice. The implementation matches display names, case-insensitively, against installed apps. Package names are a convenient engineer habit; they are a poor agent habit when the user said "Clock" and "Contacts". KDoc and app-level metadata have to say what the code accepts -- agents lean on that text harder than on your mental model of the APK. What changed in the model Before alpha10 you annotated a helper class and let the service AAR merge a stock entry point into the manifest. Starting with alpha10: @AppFunction lives in androidx.appfunctions (not androidx.appfunctions.service) It is only legal on methods of an abstract AppFunctionService marked @AppFunctionServiceEntryPoint KSP generates the concrete subclass named in serviceName and the XML named in appFunctionXmlFileName You declare that generated service yourself; nothing merges a stock one anymore There is no AppFunctionContext parameter; the service is a Context Drop appfunctions:aggregateAppFunctions. Grepping for empty app_functions. ## A2A in Java: hands on Embabel DevFeed: [A2A in Java: hands on Embabel]() Original publisher: [Read original article]() Author: Aneshka Goyal Published: 2026-06-21T07:01:03Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Embabel](), [A2A protocol](), [Java](), [MCP](), [Spring AI](), [Maven](), [bedrock](), [Large Language Model]() Tags: [a2a](), [agent](), [ai](), [embabel](), [java](), [maven](), [mcp-server](), [software-engineering](), [spring-ai]() ### AI overview A hands-on tutorial for building a Java agent with Embabel. It demonstrates LLM-based story generation and review, Amazon Bedrock integration, a local Spring AI MCP server for word counts, Maven dependency management, and A2A-compliant endpoints. ### Source excerpt Part 2: Hands on with Embabel! In Part 1, we discussed how Embabel works internally. In Part 2, we'll now try to get an application started that has an LLM interaction, talks to local MCP server (for tools), and helps us achieve a goal. This time, we'll also make sure we use A2A protocol for our agent (something Embabel makes easier to do allowing us to focus on core business logic and offloading boilerplate code to Embabel). We'll use the project creator to create a skeleton project for us with some Embabel dependencies and code. uvx --from git+https://github.com/embabel/project-creator.git project-creator Please note we can use Java or Kotlin as our preferred language, I would be leveraging Java. This is a simple story teller agent who writes a story and gets it reviewed (both story generation and review comes from LLM). We'd be using Bedrock for connection to our LLM model. For fetching the word count for a topic, it uses an MCP server which is a Spring AI MCP server running locally. Dependency management is handled using Maven, and the POM file looks like this: 4.0.0 org.springframework.boot spring-boot-starter-parent 3.5.9 com.example.demo-city-agent Demo-city-agent 0.1.0-SNAPSHOT jar My first agent Generated agent project 21 0.3.1 com.embabel.agent ) Original publisher: [Read original article]() Author: Aneshka Goyal Published: 2026-05-06T04:01:01Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Spring AI](), [Artificial Intelligence](), [Model Context Protocol](), [Amazon Bedrock](), [Spring Boot](), [Java](), [Maven](), [Large Language Model](), [Streaming]() Tags: [agentic](), [agentic-ai](), [ai](), [aws](), [developer](), [java](), [llm](), [maven](), [mcp](), [mcp-server](), [software-engineering](), [spring-ai](), [streaming]() ### AI overview A hands-on tutorial for building an agentic application with Spring AI. It demonstrates connecting an application to AWS Bedrock, exposing weather and latitude-longitude tools through a stateless MCP server over HTTP streaming, and combining MCP clients, memory, tools, and a system prompt. ### Source excerpt Part 2: Using spring AI to build a simple agentic application In Part 1 we discussed about core capabilities of Spring AI that helps it position itself as a strong framework to build Agentic applications. Taking things forward from there, let's now build something to bring things into action!! Scenario We want to build an application that connects with AWS bedrock for LLM integration. Has set of tools exposed from an MCP server running on HTTP streaming protocol in STATELESS mode(MCP is also built using Spring AI). For memory we use chat memory with inbuilt InMemory repository and MessageWindowChatMemory. This application has the ability to provide weather info, some lat long info for a particular city. MCP Server Setup Maven pom for dependency management 4.0.0 org.springframework.boot spring-boot-starter-parent 3.5.6 com.example mcp-server-demo 0.0.1-SNAPSHOT mcp-server-demo Demo project for Spring Boot 17 org.springframework.boot spring-boot-starter-web org.springframework.ai spring-ai-starter-mcp-server-webmvc 1.1.2 org.springframework.boot sprin ## Managing Sensitive Data in jOOQ 3.21+ Logs DevFeed: [Managing Sensitive Data in jOOQ 3.21+ Logs]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-03-27T12:45:19Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Logging](), [sensitive data](), [Security](), [configuration](), [Code]() Tags: [configuration](), [csv](), [debug-logging](), [jooq](), [jooq-in-use](), [json](), [logging](), [logs](), [maven](), [redacted-columns](), [security](), [sensitive-data](), [xml]() ### AI overview This article explains how jOOQ debug logging can expose query bind values and fetched records in application logs, creating security concerns in production. It describes a code-generation configuration available in commercial jOOQ distributions to mask exported data, including text, HTML, and optionally CSV, JSON, or XML output. ### Source excerpt One of jOOQ's most popular feature is the out-of-the-box debug logging experience. jOOQ developers find this feature very useful when developing their applications. Assuming you run a jOOQ query and configure your logger to print DEBUG log output: When this query is executed, your log output might contain something like this: Executing query : select ... Continue reading Managing Sensitive Data in jOOQ 3.21+ Logs -> ## Java Dependency and Classpath Problems in Gradle and Maven Builds DevFeed: [Java Dependency and Classpath Problems in Gradle and Maven Builds]() Original publisher: [Read original article]() Author: Tony Robalik Published: 2025-11-24T20:15:12Z Content type: opinion Language: en Sources: [DEV Community: Tony Robalik]() Topics: [Java](), [Gradle](), [Maven](), [Kotlin](), [Back end]() Tags: [analysis](), [build-tool](), [coding](), [community](), [compilers](), [dependencies](), [dependency](), [development](), [ecosystem](), [engineering](), [gradle](), [inclusive](), [java](), [jvm](), [kotlin](), [maven](), [software](), [software-supply-chain-attack]() ### AI overview This opinion article examines dependency and classpath problems in the Java ecosystem, including misleading metadata, fat JARs, split packages, reflection, protobuf usage, and compiler differences. It explains how classloader behavior can create conflicts and notes that classpath properties can also enable software supply-chain attacks. ### Source excerpt I am the author of the moderately popular (⭐ 2k) Dependency Analysis Gradle Plugin, a static analysis tool that helps Gradle build authors maintain a healthy dependency graph. I also maintain some of the largest Gradle repos on the planet: a Kotlin backend repo with over 2500 subprojects, and an Android repo with more than 7200 subprojects (both proprietary). I have... seen some shit. Note: I refer to both the cases above as being part of the "Java ecosystem," though both use Kotlin as the preferred language, and one runs on the JVM while the other runs on ART (the Android runtime) on mobile devices. I come to you with a simple proposition: I believe the Java ecosystem is cursed. Hear me out. We are cursed with... Lying metadata, overuse of "fat" jars with underuse of package relocation, split packages, undocumented usage of reflection to access upstream dependencies, usage of terms like "upstream" that have different meanings in different contexts, misuse of protobuffers, different compilers with different notions of their obligations vis-a-vis the Java class file format... Lying metadata This was already covered in-depth in This is why we can't have nice things: When POM files lie, but the summary is: sometimes dependencies have hand-written metadata, which is certainly A Choice given that build tools exist. I suppose it's harder to teach a build tool to lie. It's just a list, man Despite the bewildering complexity of dependency resolution engines in tools like Gradle and Maven, at the end of the day a classpath is just a list of class files (and jars that package class files). When your running program "sees" a class or interface for the first time, it has to load it. It does this with a ClassLoader. The classloader searches the classpath (just a list of class files!)1 and picks the first class file that matches the class it just encountered. Importantly, your classpath may have more than one class file for that class. Even well-behaved builds may have this problem, fo ## Dynamic configuration in Java with Server-Side Firebase Remote Config DevFeed: [Dynamic configuration in Java with Server-Side Firebase Remote Config]() Original publisher: [Read original article]() Author: Athira M Published: 2025-10-24T06:33:20Z Content type: tutorial Language: en Sources: [Firebase Developers - Medium]() Topics: [Firebase](), [Java](), [Back end](), [SDKs](), [feature flags](), [Firebase console]() Tags: [backend](), [feature-flags](), [firebase](), [firebase-console](), [firebase-remote-config](), [java](), [maven](), [remote-config](), [sdks]() ### AI overview This tutorial explains how to use server-side Firebase Remote Config with Java to externalize backend configuration and feature flags. It describes how the Java server fetches the full configuration template, evaluates conditions locally through the SDK, initializes the Firebase Admin SDK, defines safe defaults, and evaluates parameters using runtime context. ### Source excerpt Dynamic Configuration in JavaUsing Server-Side Firebase Remote Config Firebase Remote Config is a powerful, cloud-based service that lets you dynamically change your app's behavior and appearance without requiring users to update your app. It's been a game-changer for feature flags and dynamic theming on mobile and web platforms. But what about your backend, or your critical API or Java micro-service? The great news is that Firebase has expanded its support, bringing this powerful tool to the server side with SDKs for Node.js, Python, Go, and Java. This allows you to control server behavior and externalize configuration directly from the Firebase console. The key difference: where evaluation happens If you're familiar with client-side Remote Config, you know the client makes a request, and the Firebase service returns the final, evaluated configuration. The server-side model is fundamentally different: The Java server fetches the entire configuration template (parameters, values, and conditions) from the Remote Config service. The Java server then performs the condition evaluation locally, using the SDK. This shift means your server is in control, making local decisions based on attributes like user ID, location, or subscription tier. This is efficient and perfect for dynamic server logic. 🛠 Setting up Remote Config in Java Let's walk through how to integrate this into your backend, using a Payment Gateway Feature Flag as our running example. Step 1: Add the Firebase Admin SDK First, add the Firebase Admin SDK dependency to your project's configuration file (e.g., pom.xml for Maven). com.google.firebase firebase-admin 9.7.0 Step 2: Initialize the Admin SDK Your server needs secure access to Firebase. We'll use a Service Account to initialize the Admin SDK. import com.google.auth.oauth2.GoogleCredentials; import com.google.firebase.FirebaseApp; import com.google.firebase.Firebas ## Simplifying JVM App Development with Heroku's Buildpack Magic DevFeed: [Simplifying JVM App Development with Heroku's Buildpack Magic]() Original publisher: [Read original article]() Author: Andrew Fawcett Published: 2025-03-24T15:00:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Buildpacks](), [Heroku](), [Java](), [Spring Boot](), [Micronaut](), [Quarkus](), [Development]() Tags: [build-tools](), [buildpacks](), [deployment](), [developer-tools](), [engineering](), [gradle](), [heroku](), [heroku-key-value-store](), [heroku-postgres](), [java](), [languages](), [maven](), [micronaut](), [procfile](), [quarkus](), [spring-boot]() ### AI overview Heroku's Java buildpack automates much of the process of deploying JVM applications. It detects languages and frameworks, obtains build tools, configures the runtime, and can provide framework-specific settings for Spring Boot, Quarkus, and Micronaut applications. ### Source excerpt Heroku's commitment to developer productivity shines through in its powerful buildpack system. They handle the heavy lifting of building your app, letting you focus on what matters most: writing code. A prime example is the Heroku Java buildpack, a versatile tool that simplifies deploying Java applications, especially those built with popular frameworks like Spring Boot, [...] The post Simplifying JVM App Development with Heroku's Buildpack Magic appeared first on Heroku. ## How to use a project-specific Maven repository when dependency downloads fail DevFeed: [How to use a project-specific Maven repository when dependency downloads fail]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2025-01-05T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Maven](), [ci](), [Gradle]() Tags: [binaries](), [build](), [ci](), [dependencies](), [dependency](), [gradle](), [incident](), [maven]() ### AI overview This tutorial explains how to keep a project building when a Maven repository is unavailable or a dependency can no longer be downloaded. It shows how to create a project-specific local Maven repository, recover the dependency binary from the Gradle cache when available, and configure Gradle to use the local repository for that library. ### Source excerpt As developers, we've all encountered build failures in CI (or on our local machines) due to Maven repository issues preventing dependency downloads. > Could not download foo-lib-1.0.aar (org.acme.foo:foo-lib:1.0) > Could not get resource 'https://mavenrepo.com/org/acme/foo/foo-lib/1.0/foo-lib-1.0.aar'. > Could not GET 'https://mavenrepo.com/org/acme/foo/foo-lib/1.0/foo-lib-1.0.aar'. Received status code 403 from server: There could be many reasons for this: the Maven repository is currently down or is having an incident, the repository has been shut down (hello, JCenter), and the dependency is old and not republished elsewhere. ## Introducing the Keycloak Test Framework DevFeed: [Introducing the Keycloak Test Framework]() Original publisher: [Read original article]() Author: Lukas Hanusovsky Published: 2024-11-14T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Testing](), [Framework](), [Maven](), [OAuth](), [browsers](), [Chrome](), [Firefox](), [SDK]() Tags: [browsers](), [chrome](), [firefox](), [framework](), [guide](), [idm](), [kerberos](), [keycloak](), [ldap](), [maven](), [oauth](), [openid-connect](), [saml](), [sdk](), [sso](), [test](), [testing]() ### AI overview Keycloak introduces a new test framework designed to replace its current Arquillian-based test suite. The JUnit 5 extension supports custom injection, server and database lifecycles, clients and users, OAuth, UI testing, WebDriver integration, and multiple browsers. The framework is available in the main branch and nightly builds, with migration from the old testsuite beginning. ### Source excerpt How It All Started The idea to replace the current test suite has been on the table for multiple years. Initially, it was meant to be only a refactoring of the current approach on how to write tests, but after a few internal discussions and refactor updates it turned out a new test suite, based on a new framework would be a better solution. It would be good to mention a few drawbacks, that stand out when working with the current test suite. First of all, is the complexity of various configurations and additions made on top of the Arquillian framework. These changes make the test suite powerful, but the cons is that without proper documentation for beginners is almost unreadable. The second thing has the same importance, the Arquillian framework is not fully supported anymore. Other things to mention are a complicated execution system, where you want to specify what exactly should be tested, then abstract classes with shared configurations and missing the option to add a custom extension. Brighter Future? The Keycloak team began an effort to design a new test framework in May 2024. It started with a prototype to verify if our ideas were feasible. The prototype is a JUnit5 Extension based on the JUnit5 testing framework, specifically to implement JUnit5 callback classes which extend the default test lifecycle functionality and provide custom inject annotations, like @KeycloakIntegrationTest, @InjectWebDriver or @InjectRealm. After a successful test round, we've continued with a proof of concept extending features list to support multiple server modes, different databases and WebDrivers, clients and users setup, SmallRye configuration support, OAuthClient based on Nimbus SDK (this feature is a preview only) etc. The full list of currently implemented features is: Maven BOM Core module Server lifecycle Database lifecycle Admin client injection Realm, User, Client lifecycle and injection Event and Admin event listener and injection OAuth client injection UI module WebDri ## Keycloak Client Libraries 26.0.0 released DevFeed: [Keycloak Client Libraries 26.0.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2024-10-04T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [client](), [Maven]() Tags: [client](), [compatibility](), [idm](), [java](), [kerberos](), [keycloak](), [keycloak-client-libraries-release](), [ldap](), [maven](), [migration-guide](), [openid-connect](), [release](), [saml](), [sso](), [version]() ### AI overview Keycloak Client Libraries 26.0.0 introduces an independent release cycle for selected client libraries. The release also supports testing client libraries with the same server version and a few previous major server versions. ### Source excerpt Highlights Dedicated release cycle for the client libraries From this release, some of the Keycloak client libraries will have release cycle independent of the Keycloak server release cycle. The 26.0.0 release may be the last one when the client libraries are released together with the Keycloak server. But from now on, the client libraries may be released at a different time than the Keycloak server. The client libraries are these artifacts: Java admin client - Maven artifact org.keycloak:keycloak-admin-client Java authorization client - Maven artifact org.keycloak:keycloak-authz-client Java policy enforcer - Maven artifact org.keycloak:keycloak-policy-enforcer It is possible that in the future, some more libraries will be included. Compatibility of the client libraries with the server Beginning with this release, we are testing and supporting client libraries with the same server version and a few previous major server versions. Upgrading Before upgrading refer to the migration guide for a complete list of changes. ## Keycloak 24.0.5 released DevFeed: [Keycloak 24.0.5 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2024-06-04T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [OpenID connect (OIDC)](), [Security](), [Authentication](), [LDAP](), [Cypress](), [Maven]() Tags: [authentication](), [bugs](), [client](), [cypress](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [maven](), [migration](), [openid-connect](), [release](), [saml](), [security](), [sso]() ### AI overview Keycloak 24.0.5 is released with a fix for a security issue affecting some OIDC confidential clients using PAR with client_secret_post authentication. Users of this configuration are encouraged to rotate client secrets after upgrading. The release also includes enhancements, migration guidance, and resolved bugs. ### Source excerpt To download the release go to Keycloak downloads. Highlights Security issue with PAR clients using client_secret_post based authentication This release contains the fix of the important security issue affecting some OIDC confidential clients using PAR (Pushed authorization request). In case you use OIDC confidential clients together with PAR and you use client authentication based on client_id and client_secret sent as parameters in the HTTP request body (method client_secret_post specified in the OIDC specification), it is highly encouraged to rotate the client secrets of your clients after upgrading to this version. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #29073 Use cache.compute() method to improve the replace retry loop #29280 Update Create Realm in Keycloak 24 Getting Started Bugs #29129 JGroups creates log messages as it switched internally to "trace" dist/quarkus #29206 LDAP user creation reports error but user is created ldap #29314 Clicking the "save" button multiple times in the Saml IDP configuration page corrupts the value of "AuthnContext ClassRefs" admin/ui #29458 Empty CSP header value breaks security filter authentication #29471 Cypress tests store videos even for passing tests ci #29525 Maven clean build doesn't clean admin client generated files ci #29554 Cypress failing on video recording ci #29625 Database driver install examples can lead to permission errors in some circumstances docs ## jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more DevFeed: [jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-15T16:30:41Z Content type: release Language: en Sources: [jOOQ]() Topics: [releases](), [DuckDB](), [CockroachDB](), [Maven](), [Gradle](), [rdbms](), [Multi-tenancy]() Tags: [cockroachdb](), [cockroachdb-23](), [duckdb](), [gradle](), [gradle-plugin](), [implicit-joins](), [java-8](), [join-paths](), [jooq](), [jooq-3-19](), [jooq-development](), [maven](), [maven-repository](), [multi-tenancy](), [oracle-23c](), [policies](), [release-notes](), [releases](), [row-level-security](), [security](), [trigger-meta-data](), [triggers](), [trino](), [trinodb](), [udt-paths](), [udts]() ### AI overview The jOOQ 3.19.0 release adds experimental DuckDB support, Trino support, and support for CockroachDB 23 and Oracle 23c. It also improves join paths, introduces an official Gradle plugin and a commercial Maven repository, and adds policies for row-level security. ### Source excerpt New Dialects It's been a few releases since we've added support for new dialects, but finally some very interesting RDBMS of increasing popularity have joined the jOOQ family including: These dialects are available in all jOOQ editions. New dialect versions In addition to these entirely new dialects, big new CockroachDB and Oracle versions have shipped: ... Continue reading jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more -> ## 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 -> ## Farewell from the Reproducible Builds Summit 2023! DevFeed: [Farewell from the Reproducible Builds Summit 2023!]() Original publisher: [Read original article]() Published: 2023-11-02T00:00:00Z Content type: news Language: en Sources: [reproducible-builds.org]() Topics: [reproducible builds](), [reproducibility](), [builds](), [Embedded Systems]() Tags: [adb](), [apache](), [buildroot](), [builds](), [coreboot](), [debian](), [dockerignore-usage](), [fedora](), [germany](), [github](), [linux](), [maven](), [openwrt](), [org](), [reproducibility](), [reproducible-builds](), [security](), [summit](), [systemd](), [ubuntu]() ### AI overview A recap of the seventh Reproducible Builds summit in Hamburg, Germany, covering project updates, reproducibility practices, verification services, filesystem images and containers, package reproducibility, SBOMs, and related discussions. ### Source excerpt Farewell from the Reproducible Builds summit, which just took place in Hamburg, Germany: This year, we were thrilled to host the seventh edition of this exciting event. Topics covered this year included: Project updates from openSUSE, Fedora, Debian, ElectroBSD, Reproducible Central and NixOS Mapping the "big picture" Towards a snapshot service Understanding user-facing needs and personas Language-specific package managers Defining our definitions Creating a "Ten Commandments" of reproducibility Embedded systems Next steps in GNU Guix' reproducibility Signature storage and sharing Public verification services Verification use cases Web site audiences Enabling new projects to be "born reproducible" Collecting reproducibility success stories Reproducibility's relationship to SBOMs SBOMs for RPM-based distributions Filtering diffoscope output Reproducibility of filesystem images, filesystems and containers Using verification data A deep-dive on Fedora and Arch Linux package reproducibility Debian rebuild archive service discussion ... as well as countless informal discussions and hacking sessions into the night. Projects represented at the venue included: Debian, openSUSE, QubesOS, GNU Guix, Arch Linux, phosh, Mobian, PureOS, JustBuild, LibreOffice, Warpforge, OpenWrt, F-Droid, NixOS, ElectroBSD, Apache Security, Buildroot, Systemd, Apache Maven, Fedora, Privoxy, CHAINS (KTH Royal Institute of Technology), coreboot, GitHub, Tor Project, Ubuntu, rebuilderd, repro-env, spytrap-adb, arch-repro-status, etc. A huge thanks to our sponsors and partners for making the event possible: Event facilitation Platinum sponsor If you weren't able to make it this year, don't worry; just look out for an announcement in 2024 for the next event. ## Keycloak 22.0.4 released DevFeed: [Keycloak 22.0.4 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2023-10-04T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Documentation](), [API](), [JavaScript](), [Maven](), [LDAP](), [saml]() Tags: [api](), [bugs](), [database-migration](), [documentation](), [idm](), [javascript](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [maven](), [openid-connect](), [release](), [saml](), [sso]() ### AI overview Keycloak 22.0.4 is released with enhancements to the Admin Console, documentation, email validation guidance, manual database migration documentation, and JavaScript adapter distribution. The release also resolves issues involving LDAP, SAML, authentication, the UI, the Admin API, Windows, Linux, and other components. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues Enhancements #17733 Improve feature (detection) code in the Admin Console keycloak admin/api #23066 Remove bearer-only content from the Server Administration Guide keycloak docs #23124 Move email validation change docs to migration guide of 22.0.3 keycloak docs #23177 Move email validation change docs to migration guide of 22.0.4 keycloak docs #23246 Improve documentation about manual database migration keycloak docs #23312 Deploy JavaScript adapter to Maven repository keycloak Bugs #11931 user first name not refreshed in Keycloak V2 theme keycloak account/ui #21935 Using truststore with LDAP and StartTLS is not working keycloak ldap #22185 Can't boot Keycloak server with Java KeyStore p12 file running on Windows 10/2019 keycloak dist/quarkus #22478 Custom User Provider SPI: MULTIVALUED_STRING_TYPE value isn't correctly displayed on ui (but correctly saved and retrieved) keycloak admin/ui #22778 Deep link format for redirect uri parameter is not parsed correctly keycloak core #22825 Keycloak 22.0.1 unable to create user with long email address keycloak admin/api #22839 Linux Firefox + Keycloak 22.0.1 issue(continuation of issue 21307) keycloak authentication #22892 Not-working link during adding a SAML Identity provider keycloak admin/ui #22923 Events filter by IP Address not working keycloak admin/api #22974 NullpointerException when using encrypted SAML assertions keycloak saml #23053 KC22: Issue with FIPS140 in non approved mode. keycloak core #23065 Admin console throwing 403 error when logged in for sub realm using local admin user keycloak admin/ui #23185 Registration page not showing username when edit username is not enabled keycloak user-profile #23251 SAML Encryption Key Export Downloads Signing Key keycloak admin/ui #23258 Race condition inside Keycloak build chain execution keycloak dist/quarkus #23 ## Meet "YCharts": an Opensource Jetpack Compose chart library. DevFeed: [Meet "YCharts": an Opensource Jetpack Compose chart library.]() Original publisher: [Read original article]() Author: Codeangi Published: 2023-07-13T06:29:03Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Graphs](), [Library](), [ui](), [Code]() Tags: [android](), [charts](), [charts-and-graphs](), [color](), [compose](), [electronics](), [graphs](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [library](), [maven](), [signal](), [time](), [ui]() ### AI overview This article introduces Y-Charts, an open-source Jetpack Compose chart library for Android. It explains how the library integrates charts into existing UI, can be added through Maven, and supports customizable Cartesian, bar, line, and wave charts. ### Source excerpt Meet "Y-Charts": an Opensource Jetpack Compose chart library. GitHub - yml-org/YCharts: YCharts is a graph library for Android. Y-Charts is a Jetpack Compose-based charts/graphs library that enables developers to easily integrate various types of charts/graphs into their existing UI to visually represent statistical data. Jetpack Compose is Android's recommended modern toolkit for building native UI. Y-Charts leverages on powerful features of Jetpack Compose to deliver accurate and accessible results for users, and many reusable components allow it to be concise and lightweight also enabling developers to customize and add new charts with ease. Y-Charts Sample in action.Adding Y-charts to your project. You can add the library via Maven: https://medium.com/media/f3feb939f36855b0cec632a08a6c6fa8/hrefCharts in Y-Charts:1. Cartesian Charts: Cartesian charts, also known as coordinate charts or xy-charts, utilize a rectangular coordinate system with two perpendicular axes: the x-axis (horizontal) and the y-axis (vertical). These charts are particularly effective for displaying quantitative data and relationships between variables. AxisData: The AxisData model supplied to each chart item controls the behavior and appearance of X and Y axis labels, user can opt for default behavior via the builder and can customize according to their needs. Bar Charts: Bar charts use rectangular bars to represent data, where the length or height of each bar corresponds to its value. Y-Charts provides many customization including the orientation of the bar chart to achieve a horizontal-scroll behavior, along with grouping and stacking of bars. This enables users to visualize different types of bar charts with very few code changes. BarchartData and GroupBarChartData enable users to customize this behavior, additionally, users can change the appearance of the bars by using the BarStyle property. BarData represents the data for each bar shown in the chart. Following snippet shows the BarchartD ## Cannot resolve symbol 'VERSION\_3\_17' in jOOQ generated code DevFeed: [Cannot resolve symbol 'VERSION\_3\_17' in jOOQ generated code]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-30T06:56:20Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Compiler](), [Code generation](), [Gradle](), [Maven]() Tags: [code-generation](), [compilation](), [compilation-error](), [compiler](), [errors](), [gradle](), [java](), [jooq](), [jooq-in-use](), [location](), [maven]() ### AI overview This article explains that a VERSION_3_17 compilation error in jOOQ-generated code is caused by a mismatch between the runtime library and code generation library. The runtime version must be at least as new as the code generation version; matching both versions is recommended. ### Source excerpt Starting with jOOQ 3.16 and #12601, there may be a compilation error with a message like this in your jOOQ generated code: [ERROR] .../DefaultCatalog.java:[53,73] cannot find symbol[ERROR] symbol: variable VERSION_3_17[ERROR] location: class org.jooq.Constants Typically, this error is mixed with other compilation errors in generated code. Its purpose is to help troubleshoot these other compilation errors. ... Continue reading Cannot resolve symbol 'VERSION_3_17' in jOOQ generated code -> ## How to Integration Test Stored Procedures with jOOQ DevFeed: [How to Integration Test Stored Procedures with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-22T12:36:00Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Testing](), [Database](), [Testcontainers](), [Java](), [PostgreSQL]() Tags: [code](), [code-generation](), [database](), [gradle](), [how-to](), [integration-test](), [integration-testing](), [java](), [jooq](), [jooq-in-use](), [junit](), [maven](), [stored-procedures](), [testcontainers](), [unit-test]() ### AI overview This tutorial explains how to integration-test database stored procedures and functions with Java, jOOQ, Testcontainers, and JUnit. It shows how to run PostgreSQL in Testcontainers, generate jOOQ classes for stored procedures, and reuse Java test infrastructure instead of manually binding to procedures through JDBC. ### Source excerpt When you write stored procedures and functions in your database, you want to ensure their correctness, just like with your Java code. In Java, this is done with unit tests, typically with JUnit. For example, if you have the following code in Java: Then, you might write a test like this: But how do we ... Continue reading How to Integration Test Stored Procedures with jOOQ -> ## Create Dynamic Views with jOOQ 3.17's new Virtual Client Side Computed Columns DevFeed: [Create Dynamic Views with jOOQ 3.17's new Virtual Client Side Computed Columns]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-06-30T14:46:35Z Content type: article Language: en Sources: [jOOQ]() Topics: [SQL](), [PostgreSQL]() Tags: [client-side-computed-columns](), [computed-columns](), [java](), [jooq](), [jooq-3-17](), [jooq-development](), [maven](), [sql](), [virtual-client-side-computed-columns](), [virtual-computed-columns]() ### AI overview This article explains jOOQ 3.17's client-side computed columns, which let developers define computed expressions that are substituted into SQL statements or evaluated when values are written. It contrasts them with server-side computed columns and discusses using the feature to create dynamic view-like behavior without database views. ### Source excerpt One of jOOQ 3.17's coolest new features are client side computed columns. jOOQ 3.16 already added support for server side computed columns, which many of you appreciate for various reasons. What's a computed column? A computed column is a column that is derived ("computed") from an expression. It cannot be written to. It works like ... Continue reading Create Dynamic Views with jOOQ 3.17's new Virtual Client Side Computed Columns -> ## Converting Gradle convention plugins to binary plugins DevFeed: [Converting Gradle convention plugins to binary plugins]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2022-04-17T06:30:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Gradle](), [configuration](), [build performance](), [modules](), [Maven](), [Android Library]() Tags: [build](), [compilation](), [configuration](), [convention-plugins](), [dependencies](), [development-process](), [gradle](), [incremental](), [maven](), [modules](), [plugins](), [publishing]() ### AI overview This tutorial explains why Gradle convention plugins may be converted into binary plugins. It discusses IDE support and incremental build issues, then describes distributing plugins as Maven dependencies to avoid repeated compilation and simplify reuse across projects. ### Source excerpt Gradle's convention plugins are a fantastic way to share common build configuration, why not take them a step further? ## 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. ## Deploy your internal libraries on Github DevFeed: [Deploy your internal libraries on Github]() Original publisher: [Read original article]() Author: Romain Boisselle Published: 2021-04-27T05:20:12Z Content type: tutorial Language: en Sources: [Kodein Koders - Medium]() Topics: [GitHub](), [Gradle](), [Maven Central]() Tags: [bintray](), [build](), [dependency](), [github](), [gradle](), [gradle-plugin](), [how-to](), [http](), [maven](), [maven-central](), [open-source](), [plugin](), [releases](), [repo](), [tutorial]() ### AI overview This tutorial explains how to publish internal libraries or early-access releases outside Maven Central by hosting Gradle plugin releases in a GitHub repository branch and serving them over HTTP. It also explains why the authors chose this approach instead of GitHub Packages, which requires authentication even for public packages. ### Source excerpt In a previous tutorial, I explain how to configure and deploy your libraries to Maven Central. But, there are some libraries that that do... Continue reading on Kodein Koders " ## 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. [Next page]()