Filip Hrisafov opened MDEP-907 and commented
I am creating this bug in the Maven Compiler Plugin. However, I am not sure whether this is the right place. I appologize in advance if this is the wrong project.
I have noticed that using mvn dependency:go-offline will not resolve the dependencies defined in the annotationProcessorPaths of the maven-compiler-plugin.
I have created https://github.com/filiphr/maven-dependency-offline-annotation-processor-paths that demonstrates the problem.
I've had a look at MCOMPILER-391, but I don't think that this is related to this one. However, I also found MNG-6877 which might solve the problem if there is a dedicated scope for annotation processing and then the maven-dependency-plugin will correctly be able to resolve the annotation processors.
No further details from MDEP-907
Filip Hrisafov opened MDEP-907 and commented
I am creating this bug in the Maven Compiler Plugin. However, I am not sure whether this is the right place. I appologize in advance if this is the wrong project.
I have noticed that using
mvn dependency:go-offlinewill not resolve the dependencies defined in theannotationProcessorPathsof the maven-compiler-plugin.I have created https://github.com/filiphr/maven-dependency-offline-annotation-processor-paths that demonstrates the problem.
I've had a look at MCOMPILER-391, but I don't think that this is related to this one. However, I also found MNG-6877 which might solve the problem if there is a dedicated scope for annotation processing and then the maven-dependency-plugin will correctly be able to resolve the annotation processors.
No further details from MDEP-907