redhat-developer / redhat-developer/vscode-java
Multi-module Maven project does not work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I created a multi-module Maven project and tried to open the root folder in Visual Studio Code. When I try to work with any of the sub-modules, I do not get any linting, formatting, refactoring, etc... I tried Add Folder to Java Source Path but that does not work either. I have no issues working with this project in other IDE's, including Eclipse.
Environment
- Operating System: Windows 10
- JDK version: 1.8.0.201
- Visual Studio Code version: 1.14.1
- Java extension version: 0.55.1
Steps To Reproduce
- Clone example project:
git clone https://github.com/hashdelta/stix-pattern-evaluator-examples.git
cd stix-pattern-evaluator-examples
git checkout develop
- Open project in VSCode
Current Result
The plugin does not recognize the children modules, thus does not provide any kind of Java semantics support - no linting, formatting, refactoring, etc...
Expected Result
You should be able to get semantics support for any Java class when you open the parent. It should be one cohesive project.
Additional Informations
The only way to work with the sub modules is by opening the module in its own VSCode instance. This does not work for me, as one of my projects consists of over 20+ modules.
I have verified in Eclipse, NetBeans, and IntelliJ that the GitHub project has no issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone the stix-pattern-evaluator-examples repository, check out develop, and open its root folder in VS Code. Compare the root-opened project with opening a module separately, checking linting, formatting, and refactoring across child modules. Done means Java semantics work cohesively for classes in every submodule; no source file or test is named, so the relevant project-import path must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100