You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only project2 is listed in the JAVA PROJECTS view.
Expected Result
Both project1 and project2 should be listed.
See the non-maven folder in the zip file for an example with two projects that are both successfully loaded (neither of them is a maven project).
Additional Informations
The motivation behind such a mixed-project-type environment is that I have a large multi-project repo with several non-maven projects. I'm adding a new project and would like to use maven there. With this issue, I can no longer open all of the projects in a single vscode window without losing some language support on the non-maven projects.
The text was updated successfully, but these errors were encountered:
snjeza
changed the title
In a folder with both maven and non-maven projects, only the maven project is imported
Importing mixed (maven,gradle,eclipse) projects
Aug 24, 2020
When VSCode scans a folder for projects, if that folder contains both a maven and a non-maven project, VSCode will only import the maven project.
Environment
Steps To Reproduce
mixed
folder in VSCode.project1/src/Test.java
)mixed-projects.zip
extension-log.txt
language-server-log.txt
Current Result
Only
project2
is listed in the JAVA PROJECTS view.Expected Result
Both
project1
andproject2
should be listed.See the
non-maven
folder in the zip file for an example with two projects that are both successfully loaded (neither of them is a maven project).Additional Informations
The motivation behind such a mixed-project-type environment is that I have a large multi-project repo with several non-maven projects. I'm adding a new project and would like to use maven there. With this issue, I can no longer open all of the projects in a single vscode window without losing some language support on the non-maven projects.
The text was updated successfully, but these errors were encountered: