desruisseaux commented on issue #1031: URL: https://github.com/apache/maven-compiler-plugin/issues/1031#issuecomment-3907514805
The bug does not seem to be in the compiler plugin. Analysis: * In a debugger, ignore the compilation of the first modules and focus on the last module: `clientproject`. * In `AbstractCompilerMojo.resolveDependencies(…)`, there is a call to Maven dependency resolver with a `allowedTypes` argument containing the following values: `CLASSES`, `MODULES`, `PROCESSOR_CLASSES`, `PROCESSOR_MODULES`. * `org.apache.maven.impl.DefaultDependencyResolver.resolve(DependencyResolverRequest)` returns a list which does not contains the dependency of type `processor`, despite this type being requested by the compiler plugin. * The dependency seems to be lost somewhere in `org.eclipse.aether.internal.impl.collect.DependencyCollectorDelegate.collectDependencies(RepositorySystemSession, CollectRequest)`. The `CollectRequest` argument contains the processor dependency, but the `DependencyResult` return value does not. * The problem seems to be in the call to `doCollectDependencies(…)` or in the lines that follow it. Debugging is a bit difficult because of multiple dependency classes with objects wrapping other objects for historical reasons (a problem [mentioned on the mailing list](https://lists.apache.org/thread/wovf23vxjq7b7z1hk4lk46fs81n61l8v)). Will need to try harder later. -- 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]
