Support Non root parent pom about jnxplus

[khalilou88]

@jbadeau for the second point it's possible with maven plugin. You can generate a parent-project and make it your parent POM. But we need a root pom as a aggregator for all projects.

• Root Pom: aggregator for all projects and for versions
• Parent project, put it where you want, you can have a parent project for libs and other for apps. And make apps parent project extend libs parent project...

You can check nx-maven e2e test for this, but yes it's need documentation

For the first point, i don't know if it's possible

[jbadeau]

Hello there,

I have tried your suggestion and it works but I noticed an issue in the affected graph. If I have a pom.xml at the repo root and I modify any other file (e.g. README.MD) in the root I get an affected graph of all the maven projects. In this case I have no project.json at the root.

I am using:

• nx: 16.7.2
• @jnxplus/nx-boot-maven: 7.3.0

Might have crept in when making the change to include parent poms as dependencies. I would be ok with the root pom being only an aggregator pom

My root pom looks like:

<?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>
  <groupId>com.foo.techradar</groupId>
  <artifactId>workspace</artifactId>
  <version>0.0.0</version>
  <packaging>pom</packaging>
  <modules>
    <module>libs/techradar</module>
  </modules>
</project>

libs/techradar is the real parent pom

[khalilou88]

this feature is tracked in this new issue: #519
during init we will give the user an option to choose a subfolder for all maven projects (another feature will be for gradle projects).
closing the issue