Skip to content

Nx-Maven-Plugin should use setPomFile for correct resolution of flatten-maven-plugin #34181

@altaiezior

Description

@altaiezior

Current Behavior

When using nx-maven-plugin 0.0.12 with flatten-maven-plugin, if the output directory is specified as some other directory than the base directory, then the resolution of the base directory fails in the next step.

Expected Behavior

The resolution of the project, its updated pom and the base directory should work as expected

GitHub Repo

https://github.com/anuragagarwal561994/nx-issues/tree/main/issue-34181

Steps to Reproduce

  1. Use flatten-maven-plugin in your project
  2. Use outputDirectory in configuration
  3. in the next step the nx lets say compile the nx build fails because it is not able to resolve the pom file as the base directory changes

Nx Report

NX   Report complete - copy this into the issue template

Node           : 24.12.0
OS             : darwin-arm64
Native Target  : aarch64-macos
npm            : 11.6.2
daemon         : Available

nx (global)  : 22.4.0-beta.5
nx           : 22.4.0-beta.5
@nx/maven    : 22.4.0-beta.5
---------------------------------------
Registered Plugins:
@nx/maven
@naxodev/gonx
---------------------------------------
Community plugins:
@naxodev/gonx : 3.0.0
---------------------------------------
Cache Usage: 0.00 B / 46.04 GB

Failure Logs

Package Manager Version

No response

Operating System

  • macOS
  • Linux
  • Windows
  • Other (Please specify)

Additional Information

No response

Metadata

Metadata

Assignees

Labels

priority: lowLow Priority (does not affect many people or not severely or has an easy workaround)scope: javaIssues related to Java and Gradletype: bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions