redhat-developer / redhat-developer/vscode-java

Maven source and dependencies are built incorrectly at initial compile time

Open
#805 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Maven
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the problem with the blz-ospl v2.7 project in VS Code, using its top-level pom.xml and the two module pom.xml files with logging enabled. Inspect the import and build-path logs first; done means initial loading resolves module sources and dependencies without requiring a file to be opened.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.