Bug#1035884: maven-debian-helper: mh_make cannot resolve parent POM when `<version>${revision}</version>` is used

[Stanislav Dimov]

Package: maven-debian-helper
X-Debbugs-Cc: stanislav.vdimov at gmail.com
Version: 2.6
Severity: normal

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.


-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy-updates
  APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500,
'jammy'), (100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.2.6-76060206-generic (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages maven-debian-helper depends on:
ii  default-jdk                     2:1.11-72build2
ii  default-jdk-headless            2:1.11-72build2
ii  libmaven-clean-plugin-java      3.1.0-1
ii  libmaven-compiler-plugin-java   3.8.1-4
ii  libmaven-jar-plugin-java        3.1.2-1
ii  libmaven-resources-plugin-java  3.1.0-1
ii  libmaven-site-plugin-java       3.6-4
ii  libplexus-velocity-java         1.2-3.1
ii  libsurefire-java                2.22.3-1
ii  libxml2-utils                   2.9.13+dfsg-1ubuntu0.3
ii  maven                           3.6.3-5
ii  maven-repo-helper               1.10
ii  unzip                           6.0-26ubuntu3.1
ii  velocity                        1.7-6

maven-debian-helper recommends no packages.

Versions of packages maven-debian-helper suggests:
ii  apt-file                      3.2.2
ii  libmaven-javadoc-plugin-java  3.0.1-4
ii  licensecheck                  3.2.14-2
pn  subversion                    <none>

-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20230510/5cb24058/attachment.htm>