Dear Maintainer,

   * What led up to the situation?
     I tried to create a deb package for a maven project I am working on
using
`mh_make`.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     I invoked `mh_make` and started filling in the required information.
When
I got to the module resolution I was greeted by an error:

```
Analysing model/pom.xml...
May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSolver
resolveDependencies
SEVERE: Error while resolving ./model/pom.xml: Dependency not found
com.mycompany.proj:project_name:pom:${revision}
May 10, 2023 3:33:12 PM org.debian.maven.packager.DependenciesSolver
resolveDependencies
SEVERE:
org.debian.maven.repo.DependencyNotFoundException: Dependency not found
com.mycompany.proj:project_name:pom:${revision}
        at org.debian.maven.repo.Repository.registerPom(Repository.java:419)
        at
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:320)
        at
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:420)
        at
org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:260)
        at
org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:922)
```

The way it is set up is that all subprojects use the `${revision}`
placeholder
to resolve the parent POM's version. I believe this was introduced in maven
3.5.
The project builds normally when `mvn package` is invoked.

   * What was the outcome of this action?
   `mh_make` crashed

   * What outcome did you expect instead?
   `mh_make` to resolve the dependency with the parent pom and continue with
the setup.