In a Java/Maven project with modules, java plugin is not able to understand parent dependencies

[palminha]

I have a Spring Boot project, with JAVA and MAVEN, with different sub-modules

In VSCode the JAVA plugin drives the compilation, and I have configured java.import.maven.enabled": true and java.dependency.syncWithFolderExplorer": true

The compilation result with Java differs from the one obtained with Maven.
For example, with Maven I get a successful compilation, but with JAVA i get some errors.

The JAVA plugin is not able to understand the module's structure.

The structure is as follows

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

To build a module with maven, i need to pass the argument -am, so that some dependencies in tha parent pom are executed.
It seems the JAVA plugin is not doing it, or not able to recognize it

[rgrunber]

Is there a pom.xml file in the root directory that specifies :

...
...
<modules>
  <module>${parent-project-folder}</module>
  <module>${module 1}</module>
  <module>${module 2}</module>
</modules>

I think the above is probably handled well, but my guess is other kinds of setups require some manual setup.

To build module-1, would you just do mvn ... -am module-1, so that the parent project is built along with module-1 ?

[palminha]

Is there a pom.xml file in the root directory that specifies :

...
...

${parent-project-folder}
${module 1}
${module 2}

I think the above is probably handled well, but my guess is other kinds of setups require some manual setup.

To build module-1, would you just do mvn ... -am module-1, so that the parent project is built along with module-1 ?

Here is the pom.xml in the parent directory

    <modules>
        <module>xxxx-resources</module>
        <module>xxxx-commons</module>
        <module>xxxx-security</module>
        <module>xxxx-api-filters</module>
        <module>xxxx-core</module>
        <module>xxxx-search</module>
        <module>xxxx-docs</module>
    </modules>

[palminha]

for "manually" compiling i'll do this in the root directory
mvn -pl xxxx-core -am

[palminha]

Is there a pom.xml file in the root directory that specifies :
...
...

${parent-project-folder}
${module 1}
${module 2}

Returning to this point, the project follows a Maven multi-module project configuration.
I don't think there is a need to declare the parent project folder as a module

[palminha]

for "manually" compiling i'll do this in the root directory mvn -pl xxxx-core -am

from maven documentation:

-pl => Comma-delimited list of specified reactor projects to build instead of all projects. A project can be specified by [groupId]:artifactId or by its relative path

-am,--also-make => If project list is specified, also build projects required by the list

[rgrunber]

I think this would be accomplished with eclipse-m2e/m2e-core#904 . Currently there's no way to know that -am (or -amd) would be required. The extension works best when when something like mvn clean package is enough to build all (most) of the modules successfully without other customization.

[palminha]

I think this would be accomplished with eclipse-m2e/m2e-core#904 . Currently there's no way to know that -am (or -amd) would be required. The extension works best when when something like mvn clean package is enough to build all (most) of the modules successfully without other customization.

that issue can be a good follow-up (let me check there).
To clarify that module dependencies are not really "customization".