Karl Heinz Marbaise created MNG-7542: ----------------------------------------
Summary: Wrong Information - multi-module project Key: MNG-7542 URL: https://issues.apache.org/jira/browse/MNG-7542 Project: Maven Issue Type: Bug Affects Versions: 4.0.0-alpha-1 Environment: Apache Maven 4.0.0-alpha-1-SNAPSHOT (1ca65c79fa4e25c4b7da027c8f8eef1b95ceced4) Maven home: /Users/khm/tools/maven Java version: 17.0.4, vendor: Eclipse Adoptium, runtime: /Users/khm/.sdkman/candidates/java/17.0.4-tem Default locale: en_DE, platform encoding: UTF-8 OS name: "mac os x", version: "12.4", arch: "aarch64", family: "mac" Reporter: Karl Heinz Marbaise Fix For: 4.0.0 I have simple [single module spring boot project for testing purposes|https://github.com/khmarbaise/m4/tree/main/spring-boot-plus-spring-data] which produces during the build the following information at the beginning of the build: {code} [INFO] Scanning for projects... [INFO] Maven detected that the requested POM file is part of a multi-module project, but could not find a pom.xml file in the multi-module root directory '/Users/khm/ws-git-soebes'. [INFO] The reactor is limited to all projects under: /Users/khm/ws-git-soebes/examples/spring-boot-plus-spring-data [INFO] {code} If I put the same project into a different directory: {{/Users/khm/ws-git-bugs-maven/m4/spring-boot-plus-spring-data}} it does **NOT** produce the output. I have defined in the pom file the parent exactly like this: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>3.0.0-M4</version> <relativePath/> <!-- lookup parent from repository --> </parent> <groupId>com.soebes.spring.example</groupId> <artifactId>employee</artifactId> <version>0.0.1-SNAPSHOT</version> {code} Based on the configuration via {{<relativePath/>}} it should never try to find a parent project...which means this is simple separated single module project... Unfortunately the given output is misleading here... -- This message was sent by Atlassian Jira (v8.20.10#820010)