Skip to content

Remove TestBench dependencies from the published POM #93

Open

Description

@scardanzan

Recreates #92 (#92), which was closed as "not planned" on 2026-11-10 during a personal cleanup of projects. Closing it did not imply that the underlying issue had been resolved.

Current status (reviewed on 2026-11-16)

Still valid.

PR #91 was closed without being merged (2026-11-09). On master, pom.xml still declares testbench-rpc 1.5.0 without <?dev-only?> markers, and there is no dev-nuke-maven-plugin or maven.flowingcode.com/releases dev-only repository. Still blocked by FlowingCode/dev-nuke-maven-plugin#4 (Java 17 requirement vs. the JDK 8/11 jobs).

This was checked by reading the code on the default branch, without building the project or running tests. The discussion on the original issue may have more context.

Original description

Consolidates the ChipFieldAddon items of FlowingCode/AddonsInternal#214 and FlowingCode/AddonsInternal#215, which are otherwise done across the other add-ons.

  • #214: mark vaadin-testbench and testbench-rpc as <?dev-only?> and add dev-nuke-maven-plugin, so they are stripped from the published POM.
  • #215: add a <?dev-only?> repository entry for https://maven.flowingcode.com/releases and bump testbench-rpc to 1.5.1, which is no longer published to Maven Central.

Both are implemented in #91.

Blocked

#91 fails the build-vaadin14 (JDK 8) and build-vaadin23 (JDK 11) jobs, because dev-nuke-maven-plugin 1.0.0 requires Java 17:

[ERROR] Required Java version 17 is not met by current version: 1.8.0_504

Blocked by FlowingCode/dev-nuke-maven-plugin#4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions