[MNG-6877] Separate scope for annotation processing

**[Stanislav Spiridonov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=foal)** opened **[MNG-6877](https://issues.apache.org/jira/browse/MNG-6877?redirect=false)** and commented

Hi, I know about annotationProcessorPaths of maven-compiler-plugin and it works somehow, but with some limitations
1.  dependencyManagement does not work for path elements (need to specify version). workaround use variable
2. if I have apt-processor as a part of the project (separate module) and use it only in the maven-compiler-plugin configuration it has been built in the last order, that brakes build
3.  the maven-compiler-plugin can use only INSTALLED artifacts, not from a reactor

Use the processor as a usual dependency is also not a case (even with provided scope)

---

**Affects:** 3.6.3

**Issue Links:**
- [MCOMPILER-391](https://issues.apache.org/jira/browse/MCOMPILER-391) annotationProcessorPaths have to follow dependencyManagement rules

3 votes, 7 watchers

Start by reviewing the maven-compiler-plugin annotationProcessorPaths behavior described in the issue, including dependencyManagement, reactor-built processors, and installed-artifact limitations. Check the linked MCOMPILER-391 context before defining the separate scope. Done should address the listed processor dependency and build-order limitations.

Written by the indexing model from the issue text.