gnodet opened a new issue, #13911: URL: https://github.com/apache/maven/issues/13911
## Summary Add an integration test that verifies an annotation processor (AP) built in the same Maven reactor can be used by a sibling module during its `compile` phase — with both the sequential and concurrent builders. ## Background Andres Almiray [reported](https://bsky.app/profile/andresalmiray.com/post/3mznzo2zaas2i) that he couldn't get this to work with Maven 3.8.x. Unlike reactor plugins (the MNG-1088 class of problem), annotation processors are discovered via a normal `<dependency>` in the POM (usually `provided` scope, or via `<annotationProcessorPaths>` in the compiler plugin config). That POM dependency gives Maven the ordering information it needs to build the AP module first — no special reactor-plugin detection is required. However, there is no IT that explicitly verifies this scenario today. ## What to test A multi-module reactor with: - `processor/` — a `jar` module that contains a `javax.annotation.processing.Processor` implementation writing a marker file - `client/` — a `jar` module that declares `processor` as a `provided` dependency and verifies the generated output exists after `compile` Verify this works with: 1. Standard (sequential) builder — `mvn compile` 2. Concurrent builder (Maven 4+) — `mvn compile -b concurrent` Also add the scenario to `apache/maven-integration-testing` for Maven 3.10.x compatibility. -- 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]
