Release process for Node.js and Java applications

General
1

My project consists of:

  • apps\java\** - Java backend applications
  • apps\node\** - Angular frontend applications

So far, I can successfully build my entire project (both backend and frontend like this)

nx run-many -t install

Now, I want to make a release - but the release process fails

nx release patch --dry-run --first-release

relevant part of nx.json:

  "release": {
    "projects": ["apps/**"]
  },

Result: release fails on the Java app

 NX   The project "my-java-service" does not have a package.json
      available at apps\java\my-java-service\package.json.

To fix this you will either need to add a package.json file at that location, or configure
"release" within your nx.json to exclude "my-java-service" from the current release group,
or amend the packageRoot configuration to point to where the package.json should be.

It seems the release process works fine for my frontend apps, but it is expecting my Java app to have a package.json. Obviously, my Java apps do not have package.json (they have a pom.xml)

How can I configure nx release to work with my Java apps?

It’s so nice to have apps\node and apps\java in the same monorepo. I’d rather build and release them all together from same monorepo (if possible).