Recognize submodules with alternative pom.xml (not in subfolders)

[barulheira]

Describe the bug
In a modular project, when a submodule is especified not in a subfolder but in an alternative pom.xml, such as "java.xml", the IDE does not recognize its Java source folders. Autocomplete does not work, etc.

To Reproduce
Create a modular Maven project. Create a submodule with a pom.xml file called "java.xml", pointing its java source folders to inside the main project folder. Put some Java files in there.

Expected behavior
Opening those Java files, the IDE recognizes them in context, autocomplete works fine. Those Java classes become available to other submodules which point to this one.

Environments (please complete the following information as much as possible):

• OS: FreeBSD
• VS Code version: 1.99
• Extension version 0.44.0

[palminha]

The same is happening to me. My project has the following structure:

parent project -> pom.xml in the root directory of the project
modules, each one in its each sub-directory
|- module 1 -> pom.xml
|- module 2 -> pom.xml

The problem is that if I click on a sub-project and select compile, it will try to compile like this:
mvn compile -f "/full-path/project-root/module/pom.xml"

I already tried to add the -am flag (using the setting "maven.executable.options": "-am", but still it fails to understand that the parent project has a pom file.
mvn compile -f "/full-path/project-root/module/pom.xml" -am

In my command line if i use this approach using -pl in the project root, the project compiles perfectly:
mvn -pl module compile -am