slachiewicz opened a new pull request, #39: URL: https://github.com/apache/maven-executor/pull/39
`org.apache.groovy:groovy-jsr223` sits in the root `dependencyManagement` and no module declares it, so the managed version governs nothing and `dependency:tree` never mentions it. It arrived in `0e864b3` alongside `maven-batch-executor`, whose `Interpolator` and `Tool` classes drove a JSR-223 engine, and it is a real dependency in that module's POM. `991f66f` deleted the whole module and left the managed entry behind. No source, test, or resource in the repository references `javax.script`, a `ScriptEngine`, or Groovy today. A dead managed entry is not free. Dependabot cannot tell it apart from a live one, so it keeps opening bumps that no reviewer can evaluate against a classpath, and a red or cancelled CI run on one of them invites a hunt for a regression that cannot exist. #37 is the current example. Removing the entry rather than wiring it to a module is the right call here because there is nothing to wire it to. Should the batch module return under #1, the entry belongs back in the same commit as the module that consumes it. Verified: `mvn -B verify` → `BUILD SUCCESS`, 60 tests in `maven-executor` (2 skipped) and 1 each in the two provider modules (both skipped), unchanged from `main`. `spotless:apply` runs in `process-sources` from `maven-parent` 49 and reported no changes. *This change was created with AI assistance.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
