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 と 2 つのモジュールの pom.xml ファイルで logging を有効にして、問題を再現します。まず import と build-path のログを調査します。初期ロードで、ファイルを開かなくてもモジュールのソースと依存関係が解決されれば完了です。