-
Notifications
You must be signed in to change notification settings - Fork 84
Closed
Labels
bugSomething isn't workingSomething isn't working
Milestone
Description
If the [vs-code] [workspace] contains more than a single folder like:
{
"folders": [
{
"path": "../projects/projectA"
},
{
"path": "../projects/projectB"
}
]
}
and both [projectA] and [projectB] are multi-module maven projects like:
[projectA]
+ [moduleA.1]
+ [moduleA.2]
[projectB]
+ [moduleB.1]
+ [moduleB.2]
The expected java projects at the [Java Projects] view should be:
[Java Projects]
+ [projectA]
+ [moduleA.1]
+ [moduleA.2]
+ [projectB]
+ [moduleB.1]
+ [moduleB.2]
BUT the parent maven projects are being detected as java projects and the [Java Projects] view is like:
[Java Projects]
+ [projectA]
+ [moduleA.1]
+ [moduleA.2]
+ [projectA] <-- this is NOT a java project
+ [projectA] <-- this is NOT a java project
+ [projectB]
+ [moduleB.1]
+ [moduleB.2]
+ [projectB] <-- this is NOT a java project
+ [projectB] <-- this is NOT a java project
If the [vs-code] workspace contains a SINGLE folder:
{
"folders": [
{
"path": "../projects/projectA"
}
]
}
then the [Java Projects] view is OK:
[Java Projects]
+ [moduleA.1]
+ [moduleA.2]
(the parent project is NOT detected as a [java project])
Checked in [vs-code] insiders preview 1.72.0
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working