annotationProcessorPaths not firing during compile

I have a pom.xml that uses annotationProcessorPaths on the maven-compiler-plugin to process annotations. During a standard maven compile the annotations are properly processed, but not during a vs-code build (auto, or forced full/incremental)

Environment

• Operating System: MacOS Mojave
• JDK version: openjdk 12 2019-03-19
• Visual Studio Code version: 1.39.2
• Java extension version: 0.52.0

Steps To Reproduce

1. create a maven project using micronaut (or use the attached pom.xml) mn create-app -b maven test-vscode
2. create a class test.vscode.Bean as

package test.vscode;

import javax.inject.Singleton;

@Singleton
public class Bean {


}

3. Force a build

[attach a sample project reproducing the error]
attach logs

Current Result

$ ll target/classes/test/vscode
total 16
-rw-r--r--  1 bangroot  staff   600B Oct 24 13:19 Application.class
-rw-r--r--  1 bangroot  staff   328B Oct 24 13:19 Bean.class

Expected Result

$ ll target/classes/test/vscode
total 40
-rw-r--r--  1 bangroot  staff   1.9K Oct 24 13:20 $BeanDefinition.class
-rw-r--r--  1 bangroot  staff   743B Oct 24 13:20 $BeanDefinitionClass$$AnnotationMetadata.class
-rw-r--r--  1 bangroot  staff   862B Oct 24 13:20 $BeanDefinitionClass.class
-rw-r--r--  1 bangroot  staff   600B Oct 24 13:20 Application.class
-rw-r--r--  1 bangroot  staff   328B Oct 24 13:20 Bean.class

Additional Informations

I did notice that there is no .factorypath file getting generated like happens on my spring-boot projects.

Comienza con el proyecto de ejemplo de Maven y los logs adjuntos; después, compara la compilación estándar de Maven con las compilaciones automáticas, completas e incrementales de VS Code. Investiga cómo se gestionan annotationProcessorPaths de pom.xml y si se genera .factorypath. Se considera terminado cuando la compilación de VS Code produce las clases de Micronaut generadas esperadas.