Maven source and dependencies are built incorrectly at initial compile time

When the top level pom.xml is just a wrapper for two modules, the workspace does not build correctly.
When the workspace is first loaded, references from imports or from within the source are not loaded correctly. Once a file is opened, these errors go away.

Environment

• Operating System: Linux 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64
• JDK version: openjdk version "10.0.2" 2018-07-17
• Visual Studio Code version:

Version: 1.31.1
Commit: 1b8e8302e405050205e69b59abb3559592bb9e60
Date: 2019-02-12T02:19:29.629Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-45-generic

• Java extension version:

Name: Language Support for Java(TM) by Red Hat
Version: 0.38.0

• Using Java extension pack:

Id: vscjava.vscode-java-pack
Version: 0.6.0

Steps To Reproduce

1. Open a project in vscode with the main pom.xml containing only modules and with dependencies in the modules

This can be seen in
This project. The v2.7 branch has the source issue

attach logs

Errors in debug window:

[[object Object]]src/main/com/blazingkin/interpreter [in blz-ospl] is not on its project's build path

src/main/com/blazingkin/interpreter [in blz-ospl] is not on its project's build path
	at /home/blazingkin/.vscode/extensions/redhat.java-0.38.0/dist/extension.js:1
	at /home/blazingkin/.vscode/extensions/redhat.java-0.38.0/dist/extension.js:1
	at Immediate.module.exports.T.size.setImmediate (/home/blazingkin/.vscode/extensions/redhat.java-0.38.0/dist/extension.js:1)
	at runCallback (timers.js:696)
	at tryOnImmediate (timers.js:667)
	at processImmediate (timers.js:649)

Current Result

Expected Result

Additional Informations

在 VS Code 中使用 blz-ospl v2.7 项目重现该问题，使用其顶层 pom.xml 和两个模块 pom.xml 文件，并启用日志记录。首先检查导入和 build-path 日志；当初始加载能够解析模块源代码和依赖项，而无需打开文件时，即表示完成。