Rebuild All, Rebuild Project and Reload all Maven Projects trigger maven phases up to process-test-classes

Since version 1.14.0 the actions Rebuild All, Rebuild Project and Reload all Maven Projects trigger maven phases up to process-test-classes. For us this leads to a huge performance issue (vscode even hangs up) since we use a multi project workspace with multiple maven project that each need to do some expensive stuff (javascript dojo build) in phase process-sources.
Up until now this worked in eclipse and vscode with java extension 1.13.0 like a charm, since both never executed this phase in the UI if not explicitly triggered by a maven build.
Is it by intention or is this a bug? If it is, is there any possibilty to turn this off or any other solution available?

Environment

• Operating System: Win 10
• JDK version: jdk-17.0.3.1
• Visual Studio Code version: 1.74.3
• Java extension version: 1.14.0

Steps To Reproduce

1. Import the project
2. change the file path in the ant plugin in the pom.xml to a path in your system
3. Click Rebuild All
4. Now you see, that the file is created and lines are appended whenever one of the actions is executed.

Same steps in version 1.13.0 never writes the file as the phase is not executed.

demo.zip

Current Result

Phase process-sources is executed.

Expected Result

Phase process-sources is not executed like in v1.13.0.

Additional Informations

none

Reproduisez le comportement avec le demo.zip fourni, en modifiant le chemin dans le ant plugin de pom.xml, et comparez Rebuild All entre les versions de l’extension 1.13.0 et 1.14.0. Identifiez les phases du cycle de vie Maven invoquées par ces actions ; c’est terminé lorsque process-sources n’est plus exécuté par ces actions de l’UI, conformément au résultat attendu.