Skip to content

Migration to JUnit 5 - avoid using AbstractMojoTestCase #3290

Migration to JUnit 5 - avoid using AbstractMojoTestCase

Migration to JUnit 5 - avoid using AbstractMojoTestCase #3290

Triggered via issue January 17, 2026 11:56
Status Skipped
Total duration 1s
Artifacts

stale.yml

on: issue_comment
stale  /  Manage issues, PRs with waiting-for-feedback label
stale / Manage issues, PRs with waiting-for-feedback label
stale  /  Remove waiting-for-feedback label
stale / Remove waiting-for-feedback label
Fit to window
Zoom out
Zoom in