Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -1078,6 +1078,16 @@ under the License.
<artifactId>maven-resolver-tools</artifactId>
<version>${resolverVersion}</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding maven-core with ${project.version} as a plugin dependency in the graph profile of the root pom introduces a reactor cycle (maven-api-annotations → maven-api → maven → maven-core → maven-api-annotations). Since the graph profile auto-activates on non-Windows, this breaks all Maven commands on a clean checkout.

Consider relocating the page generation step to a leaf module (e.g., apache-maven) that can depend on maven-core without creating a cycle.

<artifactId>maven-core</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-compat</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
<executions>
<execution>
Expand Down
Loading