You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remove TestBench dependencies from the published POM #93
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.
Activity