# maven-plugin Published articles for maven-plugin. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts DevFeed: [App Intents: One Java Declaration for Siri, Spotlight, and Shortcuts]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-08-27T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Java](), [App](), [Android](), [iOS](), [Maven]() Tags: [android](), [app](), [build](), [bytecode](), [ios](), [java](), [maven-plugin](), [native](), [shortcuts](), [spotlight]() ### AI overview Codename One App Intents use Java annotations to generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and internal application commands. The article explains build-time validation, entity parameters, routing, and concurrent handler execution. ### Source excerpt Codename One App Intents generate reflection-free handlers for Siri, Spotlight, Shortcuts, Android launcher shortcuts, and an application command layer from Java annotations. ## OpenAPI, ORM, SVG and Lottie DevFeed: [OpenAPI, ORM, SVG and Lottie]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-01T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [OpenAPI Specification](), [Code generation](), [SQLite](), [Object-relational mapping](), [JSON](), [XML](), [SVG](), [ASP.NET Core](), [FastAPI](), [Nest]() Tags: [build](), [fastapi](), [http](), [java](), [json](), [lottie](), [maven-plugin](), [net](), [openapi](), [orm](), [rest](), [spring](), [svg](), [xml]() ### AI overview A Codename One release follow-up describes a shared build-time code generation pipeline for OpenAPI client generation, a SQLite ORM, JSON and XML mappers, SVG and Lottie transcoders, and a declarative router. The pipeline emits typed Java from annotations or declarative source files without reflection. ### Source excerpt An OpenAPI client generator, a JPA-shaped SQLite ORM, JAXB-shaped JSON / XML mappers, build-time SVG / Lottie transcoders, and a declarative router with deep links. All on the same build-time codegen pipeline. ## Stream APIs, Swift Package Manager, Tutorial Trail Refresh, and the UWP Transition DevFeed: [Stream APIs, Swift Package Manager, Tutorial Trail Refresh, and the UWP Transition]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-20T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Java](), [iOS](), [Universal Windows Platform](), [Maven](), [Package manager]() Tags: [dependencies](), [ios](), [java](), [maven-plugin](), [swift-package](), [swift-package-manager](), [update]() ### AI overview Codename One adds built-in support for Java Stream APIs and Swift Package Manager integration for iOS dependencies, refreshes its written tutorial trail, and removes the UWP target from the Maven plugin in version 7.0.229. ### Source excerpt Codename One now includes built-in java.util.stream support, adds Swift Package Manager support for iOS dependencies, refreshes the written tutorial trail, and removes the UWP target from the Maven plugin in 7.0.229. ## Grantee Roundup: April 2021 DevFeed: [Grantee Roundup: April 2021]() Original publisher: [Read original article]() Author: Ethereum Foundation Ecosystem Support Program Published: 2021-05-03T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Hackathon](), [Solidity](), [Remix](), [Java](), [Maven](), [Dependency management](), [Library](), [migration]() Tags: [blog](), [dependency-management](), [development](), [ecosystem-support-program](), [ethereum](), [hackathon](), [java](), [jvm](), [library](), [maven-plugin](), [migration](), [projects](), [remix](), [smart-contract]() ### AI overview This Ethereum Foundation grantee roundup reports on the Ethereum India Fellowship 2.0 and its training, mentorship, hackathon participation, and participant achievements. It also describes Web3 Labs' grant-supported work on Web3j, including documentation, Maven plugin updates, Solidity dependency management, and smart contract migration support. ### Source excerpt It's always fun to hear about new grants as they're awarded, but what happens after the announcement? In this series, we'll check in on a couple of projects that are well underway - or already at the finish line. Read on to learn about some recent milestones and achievements by... ## 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 ## My first maven plugin DevFeed: [My first maven plugin]() Original publisher: [Read original article]() Published: 2019-05-10T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Maven](), [Development](), [Java]() Tags: [how-to](), [java](), [maven](), [maven-plugin](), [plugin-development]() ### AI overview A beginner tutorial on writing a custom Maven plugin. It covers the Maven plugin project packaging, required dependencies, Mojo goals and parameters, plugin logic, installation, declaration in a build, and verification. ### Source excerpt In the past, I've been doing various things with maven. Some of them were standard, some were more complicated and a couple of them were complex. For those complex solutions, I felt like I needed a plugin but I've never had enough time to write it properly. In this post, I'm going to explore the basics of writing maven plugin. Read more ## Upgrading to Eclipse Photon DevFeed: [Upgrading to Eclipse Photon]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2018-07-09T09:51:00Z Content type: tutorial Language: en Sources: [Stephen Colebourne]() Topics: [ide](), [Java](), [Java 9](), [modules](), [Maven](), [Code review](), [Test coverage](), [GitHub]() Tags: [code-coverage](), [code-quality](), [eclipse](), [github](), [how-to](), [ide](), [install](), [installations](), [java](), [java-9](), [maven-plugin](), [modules](), [plugins](), [update](), [zip]() ### AI overview A personal guide to upgrading to Eclipse Photon, covering its improved separation of test and main classpaths, support for Java 9 modules and Java 10 local variable type inference, JUnit 5, and code coverage assistance. It also describes installation options and a locally built GEBIT fork of the m2e-code-quality plugin. ### Source excerpt I use Eclipse as my Java IDE. And the new release, Photon is now out. Photon is a large release, with lots of new features. The most important is the separation of the test and main classpaths, which has always been a point of pain in the IDE. Now it just works as you would expect, and the Maven plugin M2E correctly sets it up: Note the darker colour of the src/test classpath elements. Support for Java 9 (modules) and Java 10 (local variable type inferenece) is also present, ready for Java 11 in September. You can also use JUnit 5. It even tries to help you reach 100% code coverage! All in all, I feel this is a release where upgrading will make a difference to everyday coding. I've upgraded my own Eclipse installations, and it all went pretty well. You can either start from a clean install (I prefer the basic IDE without plugins so I can choose which ones to add). Or you can add Photon as an update site, and let Eclipse update itself. One problem I had was the plugin that connects Maven (M2E) to Checkstyle (Eclipse-CS), known as m2e-code-quality. Fortunately, the team at GEBIT have been maintaining a fork of the original plugin. However, they don't release it in binary form. As such, I had to build the plugin locally (no big deal - its a simple build). To simplify the process however, I've created a repository on GitHub with my Eclipse setup files, and a binary zip of the GEBIT forked plugin. To use just the m2e-code-quality GEBIT fork, download the zip file and add it as an update site. Here are some instructions. Thank you Eclipse team for a great release! PS. I won't be answering "how to" questions about upgrading Eclipse or the eclipse-setup repository. There are plenty of other places to ask questions, such as Stack Overflow or the Eclipse Forums. ## Cluecumber Report Maven Plugin for Cucumber test reporting DevFeed: [Cluecumber Report Maven Plugin for Cucumber test reporting]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2017-11-16T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Cucumber](), [test](), [Maven](), [Java]() Tags: [css](), [frontend](), [html](), [images](), [java](), [maven](), [maven-plugin](), [monitoring](), [open-source](), [plugin](), [quality-assurance](), [release](), [reporting](), [test]() ### AI overview The article explains why trivago replaced its existing Cucumber reporting Maven plugin and describes the design of the Cluecumber Report Plugin. The new plugin uses HTML templates and generates overview and scenario-detail pages from Cucumber JSON results. ### Source excerpt We were not as happy as we could be with out Cucumber test reporting solution - so we decided to build a new and shiny one from scratch. ## Cucable Maven plugin for parallel execution of Cucumber scenarios DevFeed: [Cucable Maven plugin for parallel execution of Cucumber scenarios]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2017-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Cucumber](), [Maven](), [test](), [Selenium](), [ci]() Tags: [browser](), [ci](), [frontend](), [maven](), [maven-plugin](), [open-source](), [parallel](), [plugin](), [quality-assurance](), [speed](), [test](), [user-experience]() ### AI overview Trivago describes creating Cucable, a Maven plugin that splits Cucumber scenarios into smaller chunks for parallel execution. The article explains limitations of custom runners, tag-based execution, feature-based execution, and existing plugins, particularly for scenario outlines and CI automation. ### Source excerpt Running Cucumber scenarios in parallel can be tricky, especially when a custom test runner is used. That's why we created Cucable - a Maven plugin to split test scenarios into smaller chunks that can be run at the same time. ## Don't use junit.framework DevFeed: [Don't use junit.framework]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2014-12-14T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Maven](), [deprecated](), [Code]() Tags: [classes](), [configuration](), [deprecated](), [import](), [junit](), [maven](), [maven-plugin](), [org](), [script]() ### AI overview The article recommends replacing deprecated junit.framework imports with org.junit imports and preventing old imports from entering new code. It suggests using a Bash script for replacement and restrict-maven-plugin configuration to fail builds that contain the old imports. ### Source excerpt Every once in a while I see somewhere a wrong import to the old, deprecated junit.framework instead of org.junit. ## Maven, Gems, and a JRuby Console for All DevFeed: [Maven, Gems, and a JRuby Console for All]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-07-02T16:03:00Z Content type: tutorial Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Maven](), [Java](), [Ruby]() Tags: [dependencies](), [embedded](), [engineering](), [how-to](), [java](), [maven-plugin](), [packaging](), [ruby]() ### AI overview A tutorial showing how to package an embedded JRuby console and its gem dependencies inside a Maven shaded JAR. It explains the Maven plugin configuration and demonstrates running the application in production without invoking JRuby while still allowing the console to access the configured gems. ### Source excerpt We will show how to add a JRuby console to any maven project... with gems!