Skip to content

IT: verify annotation processor in the same reactor can be used by a sibling moduleΒ #13911

Open

Description

@gnodet

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 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.

Activity

  1. codewithsinchana commented on Nov 11, 2026

    @codewithsinchana
    Contributor

    I reviewed the integration test and the recent change removing the concurrent-builder scenario.

    I'd like to contribute to the remaining concurrent-builder issue. I understand that annotationProcessorPaths resolution currently does not use the reactor WorkspaceReader, which prevents resolving an annotation processor built in the same reactor without installing it first.

    I am interested in investigating the workspace resolution path and adding a regression test to restore concurrent-builder support.

  2. codewithsinchana commented on Nov 11, 2026

    @codewithsinchana
    Contributor

    Thanks for adding this integration test. I noticed that the PR description originally mentions verification with both sequential and concurrent builders, but the concurrent test was subsequently removed because annotationProcessorPaths resolution does not use the workspace reader. Could you clarify whether concurrent-builder support is intentionally out of scope for this issue, and whether the remaining limitation should be tracked separately under MCOMPILER-496?

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

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions