Incorrect source level detected using tiles-maven-plugin

We use the tiles-maven-plugin ( caveat, I'm also a maintainer ) for our projects and include the maven-compiler-plugin settings in a tile, which gets resolved as a parent pom in the effective-pom.

vscode-java however seems to be only looking at the XML file, and not the effective pom when detecting source/target levels - this causes a lot of strange and confusing compile/test issues when building in a terminal, and tabbing back into vscode which seems to rewrite the .class files, causing Maven a lot of confusion ( after quitting vscode - all my odd build issues go away ).

Environment

• Operating System: Mac OS
• JDK version: JDK 1.8
• Visual Studio Code version: 1.25.1
• Java extension version: 0.28

Steps To Reproduce

1. clone https://github.com/HalBuilder/halbuilder-core from github
2. "code ." in the root directory, wait for project parsing etc.

Current Result

1. Open NamespaceManager.java - lambda calls show as errors

Expected Result

2. lambda calls show correctly as valid, using the desired source/target levels.

Reproduce el comportamiento de análisis del proyecto siguiendo los pasos indicados con halbuiler-core e inspecciona NamespaceManager.java, donde las llamadas lambda se notifican incorrectamente. Empieza comparando los niveles source/target del XML y del POM efectivo, incluidos los ajustes de maven-compiler-plugin proporcionados por tiles-maven-plugin. Se considera terminado cuando se detectan los niveles deseados y las llamadas lambda aparecen como válidas sin provocar conflictos en la compilación final.